From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: line-move-ignore-invisible and global-disable-point-adjustment
Date: Sat, 05 Jan 2008 11:20:45 +0100 [thread overview]
Message-ID: <477F59FD.6080801@gmx.at> (raw)
In-Reply-To: <jwvwsqpwh88.fsf-monnier+emacs@gnu.org>
> There has not been any compelling evidence that users would ever want to
> set both of those to nil or both to t, other than by accident, so by
> removing those 2 cases we get to eliminate some bugs and also we get to
> avoid having to figure what actually *means* a combination such as "nil
> and nil" or "t and t".
We could finally concentrate on finding the "real" bugs here.
> If we agree that this is a good change, then comes the second part of
> the discussion which is about how to go about doing it: since the value
> of the those vars should be the negative of the other, we can't just use
> defvaralias, so we'll have to declare line-move-ignore-invisible as
> obsolete but still make it work (more or less) as before.
Give `line-move-ignore-invisible' the initial value `undecided', replace
all occurrences where `line-move-ignore-invisible' is set in current
Emacs by a corresponding setting of `global-disable-point-adjustment',
leave a note in the doc-string of `line-move-ignore-invisible' that this
variable is considered obsolete, and change the manual accordingly.
Now the code in `line-move-1' would do the same thing as usual for
`line-move-ignore-invisible' iff the value of this is _nil_, that is,
someone has explicitly set it despite of the obsolescence warning. If
it's t and `global-disable-point-adjustment' is t too, the latter would
prevail.
next prev parent reply other threads:[~2008-01-05 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 19:10 line-move-ignore-invisible and global-disable-point-adjustment Stefan Monnier
2008-01-05 10:20 ` martin rudalics [this message]
2008-01-05 14:31 ` Richard Stallman
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=477F59FD.6080801@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).