unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Travis Evans <travisgevans@gmail.com>, 22554@debbugs.gnu.org
Subject: bug#22554: 24.5; enriched-mode: C-S-a/S-Home doesn't mark to beginning of line
Date: Thu, 4 Feb 2016 08:46:40 -0800 (PST)	[thread overview]
Message-ID: <c9403ce4-072a-452f-a100-23741bf09528@default> (raw)
In-Reply-To: <56B3447C.6070604@gmail.com>

> After launching Emacs with ‘emacs -Q’, typing “C-x b newbuffer M-x
> enriched-mode”, then “||abcdefgfoo” followed by C-S-a or S-<Home>, point
> returns to the ‘a’ with nothing highlighted. In other modes, this key
> returns to the very beginning of the line starting with ‘|’ and with the
> line marked, as expected. C-S-e/S-<End> still works as expected in this
> and other modes. I could not find anything in the Enriched Text section
> of the Emacs manual that mentions this discrepancy.

Confirmed, in text mode.  Even just `C-a' returns to the `a' and not bol.
And this is the case at least as far back as Emacs 20.

`C-a' and `C-S-a' is bound in text mode to `beginning-of-line-text'
(not to `beginning-of-line').  The doc for that command does not
seem to cover the case of `|'.  It says only that it "moves past the
lef-margin indentation, the fill-prefix, and any indentation used
for centering or right-justifying the line".

The culprit seems to be `adaptive-fill-mode'.
(looking-at adaptive-fill-regexp) returns t.

The doc string should mention this part of the behavior, I think.

It seems that the point-moving behavior here is not a bug, but
there is a doc bug here.





  reply	other threads:[~2016-02-04 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 12:30 bug#22554: 24.5; enriched-mode: C-S-a/S-Home doesn't mark to beginning of line Travis Evans
2016-02-04 16:46 ` Drew Adams [this message]
2021-02-07 16:59 ` Lars Ingebrigtsen
2021-02-07 17:11   ` Eli Zaretskii
2021-02-07 17:15     ` Lars Ingebrigtsen
2021-02-08  6:23       ` Lars Ingebrigtsen

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=c9403ce4-072a-452f-a100-23741bf09528@default \
    --to=drew.adams@oracle.com \
    --cc=22554@debbugs.gnu.org \
    --cc=travisgevans@gmail.com \
    /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).