unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: 8920@debbugs.gnu.org
Subject: bug#8920: 24.0.50; Calendar raises error with #included diary file
Date: Thu, 23 Jun 2011 01:03:21 +0200	[thread overview]
Message-ID: <878vst8o5i.fsf@escher.fritz.box> (raw)

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

1. Let the file ~/diary consist of the line between start and end:
-----start
#include "~/test"
end------

2. Let ~/test be readable; it's content is irrelevant (can be empty).

3. Let ~/.emacs consist of the lines between start and end:
-----start
(add-hook 'find-file-hook
	  (lambda () (set-window-buffer (selected-window)
					(set-buffer (current-buffer)))))

(custom-set-variables
 '(calendar-mark-diary-entries-flag t)
 '(calendar-today-visible-hook (quote (calendar-mark-today)))
 '(diary-list-entries-hook (quote (diary-include-other-diary-files)))
 '(diary-mark-entries-hook (quote (diary-mark-included-diary-files))))
end------

4. Invoke emacs (without -Q)

5. Type `M-x calendar RET'
=> Wrong type argument: number-or-marker-p, nil
The Calendar is displayed in the lower window, but today's date is not
marked, and the cursor is at the beginning of the buffer.

Here is the backtrace from entering the debugger on error:


[-- Attachment #2: backtrace --]
[-- Type: application/octet-stream, Size: 573 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1029 bytes --]


When I repeat the above recipe through step 4, then instrument the
lambda expression in .emacs for edebugging, then invoke the Calendar and
step through the lambda sexp, the Calendar first appears, then its
window is occupied by the diary buffer, then by the buffer of ~/test,
and finally by the diary again.  No error is raised, and when I switch
to the *Calendar* buffer, today's date is shown marked.


In GNU Emacs 24.0.50.1 (i686-suse-linux-gnu, GTK+ Version 2.20.1)
 of 2011-06-04 on escher
Windowing system distributor `The X.Org Foundation', version 11.0.10800000
configured using `configure  '--without-toolkit-scroll-bars' 'CFLAGS=-g -O2 -fno-optimize-sibling-calls''

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: en_US.UTF-8
  value of $XMODIFIERS: @im=local
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

             reply	other threads:[~2011-06-22 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 23:03 Stephen Berman [this message]
2011-06-24 18:49 ` bug#8920: 24.0.50; Calendar raises error with #included diary file Glenn Morris
2011-06-24 21:32   ` Stephen Berman
2011-06-25 20:18     ` Stephen Berman
2011-06-25 22:25       ` Glenn Morris
2011-06-26  0:19         ` Stephen Berman
2011-06-26  1:25           ` Glenn Morris
2011-06-26 11:09             ` Stephen Berman

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=878vst8o5i.fsf@escher.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=8920@debbugs.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).