[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

`term-setup-hook' sometimes run before `emacs-startup-hook'

From: Matt Swift
Subject: `term-setup-hook' sometimes run before `emacs-startup-hook'
Date: Mon, 17 Feb 2003 18:48:05 -0500
User-agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.2

This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.

In GNU Emacs 21.2.1 (i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2002-11-06 on beth, modified by Debian
configured using `configure  i386-debian-linux-gnu --prefix=/usr/local 
--sharedstatedir=/var/lib --libexecdir=/usr/local/lib --localstatedir=/var/lib 
--infodir=/usr/local/share/info --mandir=/usr/local/share/man --with-pop=yes 
--with-x=yes --with-x-toolkit=athena --without-gif'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Docstring for `term-setup-hook', defined in startup.el:

    Normal hook run after loading terminal-specific Lisp code.
    It also follows `emacs-startup-hook'.  This hook exists for users to set,
    so as to override the definitions made by the terminal-specific file.
    Emacs never sets this variable itself.

According to CVS startup.el 1.312, it does not always follow

  (if (and (not inhibit-startup-message) (not noninteractive)
             (not (and (fboundp 'process-list)

                       it precedes `emacs-startup-hook'


In 21.2, it also does not always follow `emacs-startup-hook', but the
conditions are different.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]