unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Luis O. Silva" <silva@paloma.spbu.ru>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Calendar's buffer hooks
Date: Thu, 19 Sep 2002 09:32:26 +0400	[thread overview]
Message-ID: <15753.24938.525187.726221@localhost.localdomain> (raw)
In-Reply-To: <sh4rcnpucv.fsf_-_@tux.gnu.franken.de>

Karl,

On Wed, 18 Sep 2002 10:36:32 +0200, Karl Eichwalder writes:

   Karl> Simon Hooper <simon@trickshot.nu> writes:
   >> (add-hook 'calendar-mode-hook 'simon-calendar-function)

   Karl> calendar-mode-hook isn't defined.  Try:

   Karl> (add-hook 'initial-calendar-window-hook
   Karl> 'simon-calendar-function)

   Karl> I just found it's documented in the manual:

I don't know why but, when using
`initial-calendar-window-hook' in the following:

(setq-default show-trailing-whitespace t)
...
...
(add-hook 'initial-calendar-window-hook
          (lambda ()
            (setq show-trailing-whitespace nil)))

the trailing whitespace disappears only partially (!!!???) and,
after some event take place (or after some time --~30 sec.)
(!!!???), it disappears completely. The result is similar to
the one obtained using the hook: `today-visible-calendar-hook'.

Could anybody explain why this delay happens?
Thank you.

luis


-- 
Luis Octavio Silva P.
St. Petersburg State University.
66/3 Botanicheskaya St., Apt.119/2
Stary Peterhof
St. Petersburg, Russia.

  reply	other threads:[~2002-09-19  5:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-14  9:45 trailing whitespace visible on some buffers Luis O. Silva
2002-09-17 10:30 ` Calendar's buffer hooks (was trailing whitespace visible on some buffers) Luis O. Silva
     [not found] ` <mailman.1032257775.4079.help-gnu-emacs@gnu.org>
2002-09-17 10:49   ` Simon Hooper
2002-09-18  8:36     ` Calendar's buffer hooks Karl Eichwalder
2002-09-19  5:32       ` Luis O. Silva [this message]
     [not found]       ` <mailman.1032412637.13710.help-gnu-emacs@gnu.org>
2002-09-20 18:51         ` Karl Eichwalder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15753.24938.525187.726221@localhost.localdomain \
    --to=silva@paloma.spbu.ru \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).