From: E Sabof <esabof@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14346@debbugs.gnu.org
Subject: bug#14346: 24.3; beginning-of-visual-line jumps to previous line in org-mode
Date: Sat, 4 May 2013 14:27:31 +0100 [thread overview]
Message-ID: <CAEp6DyaP8N21FCxSX6tos1Cco9kCoQhK05BJM49V4qz6A406JA@mail.gmail.com> (raw)
In-Reply-To: <83y5bvkki7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Wouldn't it be better if forward/backward-char kept the old behavior, and
the rest of the commands did something similar to this in the end:
(setq disable-point-adjustment
(preceding-or-following-character-visible-p))
I'm not entirely sure whether it would be better, but at the moment, I
can't think of a case where it wouldn't.
Evgeni
On Sat, May 4, 2013 at 1:16 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 4 May 2013 12:17:35 +0100
> > From: E Sabof <esabof@gmail.com>
> > Cc: 14346@debbugs.gnu.org
> >
> > I see what you mean. But it still looks like a bug - whether I follow the
> > above recipe, or press C-e C-a, the point will (should?) go to the same
> > position, but the behavior is different.
>
> The behavior depends on the direction point was moving before ending
> up in the invisible text. It's a heuristic, and as every heuristic,
> it sometimes fails.
>
[-- Attachment #2: Type: text/html, Size: 1485 bytes --]
next prev parent reply other threads:[~2013-05-04 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 9:08 bug#14346: 24.3; beginning-of-visual-line jumps to previous line in org-mode E Sabof
2013-05-04 11:01 ` Eli Zaretskii
2013-05-04 11:05 ` Eli Zaretskii
2013-05-04 11:17 ` E Sabof
2013-05-04 12:16 ` Eli Zaretskii
2013-05-04 13:27 ` E Sabof [this message]
2013-05-07 1:34 ` E Sabof
[not found] ` <CAEp6DyaDWtuw96Hm73BA-WOdiez8O7ud0stCQSycaLS5KXkZ0A@mail.gmail.com>
2013-05-10 7:00 ` bug#14346: [O] " Carsten Dominik
2019-09-30 15:59 ` Stefan Kangas
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=CAEp6DyaP8N21FCxSX6tos1Cco9kCoQhK05BJM49V4qz6A406JA@mail.gmail.com \
--to=esabof@gmail.com \
--cc=14346@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).