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: Mon, 12 Dec 2016 18:53:43 +0200 [thread overview]
Message-ID: <83d1gxccmg.fsf@gnu.org> (raw)
In-Reply-To: <c1de5cde-5327-2e96-db42-2516b461c519@easy-emacs.de> (message from Andreas Röhler on Mon, 12 Dec 2016 12:49:05 +0100)
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> Date: Mon, 12 Dec 2016 12:49:05 +0100
>
> Bug does not appear with Emacs -Q, as some fontification in buffer seems
> to trigger it.
>
> Text in buffer:
>
> git reset HEAD test/2.sh
>
> Cursor at pos 16. i.e. beginning of word "test".
>
> C-a doesn't move point.
Please show a complete recipe, starting from "emacs -Q" (and loading
any optional packages/customizations as needed). It's hard to discuss
an issue without being able to test-drive it.
> Watching move-beginning-of-line edebug, at line 6415
>
> (skip-chars-backward "^\n")
>
> jumps correctly to BOL.
>
> Error results from following later on:
>
> (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.
Once again, if you show an actual example, it will be much easier to
decide whether there's a bug here, and if so, what is it.
Thanks.
next prev parent reply other threads:[~2016-12-12 16:53 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 [this message]
2016-12-12 19:04 ` Andreas Röhler
2016-12-13 9:25 ` Andreas Röhler
2016-12-13 16:05 ` Eli Zaretskii
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
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=83d1gxccmg.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 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).