From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 25181@debbugs.gnu.org
Subject: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 18:05:39 +0200 [thread overview]
Message-ID: <83mvfzbyr0.fsf@gnu.org> (raw)
In-Reply-To: <cb66f556-72be-a613-dc27-433df4e42f57@easy-emacs.de> (message from Andreas Röhler on Tue, 13 Dec 2016 10:25:32 +0100)
> Cc: 25181@debbugs.gnu.org
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> Date: Tue, 13 Dec 2016 10:25:32 +0100
>
> >> (setq first-vis-field-value
> >> (constrain-to-field first-vis orig (/= arg 1) t nil))
> >>
> >> Here first-vis-field-value is set to orig, i.e. pos 16, where it jumps
> >> back-to, not leaving point at BOL.
> > I'm not sure I understood, but if I did, this is a feature: functions
> > such as beginning-of-line stop moving at field boundaries.
> >
>
> Hmm, is this reasonable? BOL is a very basic concept. Don't think it
> should be permitted to be interfered with fields.
The idea is that a Lisp program would use fields only when the
produced effect is what the user would expect. You see this every day
in action when you type "C-x C-f" and then C-a: point stops at the
beginning of the default directory, without entering the "Find file:"
prompt. Moving point to BOL in this case would be a nuisance. (You
can still get to the beginning of line by other means, like C-b.)
That's what fields are all about. If you don't want this effect,
don't use fields; they are opt-in.
next prev parent reply other threads:[~2016-12-13 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 11:49 bug#25181: 25.1.90; move-beginning-of-line doesn't move point Andreas Röhler
2016-12-12 16:53 ` Eli Zaretskii
2016-12-12 19:04 ` Andreas Röhler
2016-12-13 9:25 ` Andreas Röhler
2016-12-13 16:05 ` Eli Zaretskii [this message]
2016-12-13 17:55 ` Andreas Röhler
2016-12-13 18:21 ` Eli Zaretskii
2016-12-13 20:10 ` Andreas Röhler
2016-12-13 20:04 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvfzbyr0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25181@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.