From: Carsten Dominik <carsten.dominik@gmail.com>
To: Michael Sperber <sperber@deinprogramm.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Support (or not) for Emacs 21, and XEmacs
Date: Mon, 19 Apr 2010 17:55:00 +0200 [thread overview]
Message-ID: <EE098F90-ED0A-4835-9AD2-BDB6AA08E490@gmail.com> (raw)
In-Reply-To: <y9lwrw3qvz2.fsf@deinprogramm.de>
OK.
- Carsten
On Apr 19, 2010, at 5:54 PM, Michael Sperber wrote:
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> That is acceptable - but I think that making BUFFER default to
>> (current-buffer) does make a lot of sense - which is why making that
>> argument optional in XEmacs is a good idea anyway.
>
> It would - but the problem is that in XEmacs, an omitted BUFFER
> argument
> means something different from (current-buffer):
>
> `local-variable-p' is a built-in function
> -- loaded from "/afs/informatik.uni-tuebingen.de/home/sperber/build/
> xemacs/src/symbols.c"
> (local-variable-p SYMBOL BUFFER &optional AFTER-SET)
>
> Documentation:
> Return t if SYMBOL's value is local to BUFFER.
> If optional third arg AFTER-SET is non-nil, return t if SYMBOL would
> be
> buffer-local after it is set, regardless of whether it is so
> presently.
> A nil value for BUFFER is *not* the same as (current-buffer), but
> means
> "no buffer". Specifically:
>
> -- If BUFFER is nil and AFTER-SET is nil, a return value of t
> indicates that
> the variable is one of the special built-in variables that is always
> buffer-local. (This includes `buffer-file-name', `buffer-read-only',
> `buffer-undo-list', and others.)
>
> -- If BUFFER is nil and AFTER-SET is t, a return value of t
> indicates that
> the variable has had `make-variable-buffer-local' applied to it.
>
> --
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
- Carsten
next prev parent reply other threads:[~2010-04-19 15:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:15 Support (or not) for Emacs 21, and XEmacs Carsten Dominik
2010-04-16 10:26 ` Carsten Dominik
2010-04-16 10:27 ` Carsten Dominik
2010-04-16 12:19 ` Matt Lundin
2010-04-16 16:41 ` Carsten Dominik
2010-04-16 13:03 ` Sebastian Rose
2010-04-16 13:13 ` Bernt Hansen
2010-04-16 14:39 ` Carsten Dominik
2010-04-16 14:42 ` Bernt Hansen
2010-04-16 14:42 ` Carsten Dominik
2010-04-16 19:15 ` Bernt Hansen
2010-04-16 22:02 ` Carsten Dominik
2010-04-16 13:32 ` Rémi Vanicat
2010-04-16 13:56 ` Sebastian Rose
2010-04-16 13:07 ` Jan Böcker
2010-04-16 13:47 ` Günter Kolousek
2010-04-17 15:39 ` Michael Sperber
2010-04-17 20:31 ` Carsten Dominik
2010-04-18 8:22 ` Michael Sperber
2010-04-18 14:03 ` Carsten Dominik
2010-04-19 11:00 ` Michael Sperber
2010-04-19 11:19 ` Michael Sperber
2010-04-19 15:51 ` Carsten Dominik
2010-04-19 15:54 ` Michael Sperber
2010-04-19 15:55 ` Carsten Dominik [this message]
2010-04-19 15:59 ` Carsten Dominik
2010-05-07 7:51 ` Carsten Dominik
2010-05-07 8:30 ` Michael Sperber
2010-05-07 9:21 ` Carsten Dominik
2010-04-23 15:50 ` Michael Sperber
2010-04-23 19:03 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EE098F90-ED0A-4835-9AD2-BDB6AA08E490@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sperber@deinprogramm.de \
/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/org-mode.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).