GNU bug report logs - #25181
25.1.90; move-beginning-of-line doesn't move point

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25181 in the body.
You can then email your comments to 25181 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.1.90; move-beginning-of-line doesn't move point
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.


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.

When C-a is called at or from behind word "test", it stops at pos 16, 
when called before it reaches BOL


In GNU Emacs 25.1.90.1 (i686-pc-linux-gnu, GTK+ Version 3.14.5)
 of 2016-11-29
Windowing system distributor 'The X.Org Foundation', version 11.0.11604000
System Description:    Debian GNU/Linux 8.6 (jessie)

Configured using:
 'configure --with-modules'

Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND GPM DBUS GSETTINGS NOTIFY ACL GNUTLS
LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11
MODULES

Important settings:
  value of $LANG: de_DE.utf8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix

Major mode: Shell-script

Minor modes in effect:
  shell-dirtrack-mode: t
  diff-auto-refine-mode: t
  highlight-changes-visible-mode: t
  show-paren-mode: t
  save-place-mode: t
  override-global-mode: t
  sh-electric-here-document-mode: t
  winner-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:

Result: 16 (#o20, #x10, ?\C-p)
Pos. 263500 als register "a" [2 times]
Back to top level [2 times]
move-beginning-of-line
Mark set
Pos. 263500 als register "a"
Mark set
nil
move-beginning-of-line

Message #8 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Mon, 12 Dec 2016 18:53:43 +0200

> From: Andreas Röhler <andreas.roehler <at> 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.

Message #11 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Mon, 12 Dec 2016 20:04:27 +0100

[Message part 1 (text/plain, inline)]

On 12.12.2016 17:53, Eli Zaretskii wrote:
>> From: Andreas Röhler <andreas.roehler <at> 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.

Unfortunately didn't found a way from "emacs -Q" yet.
Attach a png displaying the property at stopping point.

BTW copied the text after stop-column --i.e. after "git reset HEAD"-- 
from a shell-buffer.
Maybe the properties have been taken from there?

[prop.png (image/png, attachment)]

Message #14 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 10:25:32 +0100

On 12.12.2016 17:53, Eli Zaretskii wrote:
>> From: Andreas Röhler <andreas.roehler <at> 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.
>

Hmm, is this reasonable? BOL is a very basic concept. Don't think it 
should be permitted to be interfered with fields.

Message #17 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 18:05:39 +0200

> Cc: 25181 <at> debbugs.gnu.org
> From: Andreas Röhler <andreas.roehler <at> 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.

Message #20 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 18:55:10 +0100

On 13.12.2016 17:05, Eli Zaretskii wrote:
>>
>> 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.

Felt rather having been  ad-opted ;) Still think there is a bug - might 
be a seldom one.

Message #23 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 20:21:45 +0200

> Cc: 25181 <at> debbugs.gnu.org
> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
> Date: Tue, 13 Dec 2016 18:55:10 +0100
> 
> Still think there is a bug - might be a seldom one.

I didn't say I disagreed, but I do need to see a recipe to look into
this any further.

Message #26 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 21:10:46 +0100

On 13.12.2016 19:21, Eli Zaretskii wrote:
>> Cc: 25181 <at> debbugs.gnu.org
>> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
>> Date: Tue, 13 Dec 2016 18:55:10 +0100
>>
>> Still think there is a bug - might be a seldom one.
> I didn't say I disagreed, but I do need to see a recipe to look into
> this any further.

I'd say the bug-source is visible by design. Such things like mentioned 
by docu:

"To ignore intangibility, bind `inhibit-point-motion-hooks' to t" IMHO 
don't belong onto such a general command.

Adapting C-a to intangibility or related things should be up to the 
mode. WRT to your example find-file, probably it would be at the 
minibuffer to care for an appropriate C-a then.

Message #29 received at 25181 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Cc: 25181 <at> debbugs.gnu.org
Subject: Re: bug#25181: 25.1.90; move-beginning-of-line doesn't move point
Date: Tue, 13 Dec 2016 22:04:51 +0200

> Cc: 25181 <at> debbugs.gnu.org
> From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
> Date: Tue, 13 Dec 2016 21:10:46 +0100
> 
> I'd say the bug-source is visible by design.

If it's by design, then it isn't a bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.