emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)]
Date: Thu, 20 Jul 2023 22:55:33 +0200	[thread overview]
Message-ID: <39c22e30-de2c-09cb-091d-d26e83f55436@vodafonemail.de> (raw)
In-Reply-To: <87edl53ae3.fsf@localhost>

On 2023-07-18  10:13, Ihor Radchenko wrote:

> No, it is space. In particular, it is `org--align-tags-here' + some bug
> in Emacs that screws up column computation.
> 
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64696

FWIW the third test yields

  ■  Warning (emacs): Test #3:: ’word’ is hidden applying ’invisible 
text property to heading body.
  ■  Warning (emacs): Moved point after first ’word’
  ■  Warning (emacs): 1:: current-column = 0
  ■  Warning (emacs): redisplayed
  ■  Warning (emacs): 2:: current-column = 0
  ■  Warning (emacs): Indented to column 50
  ■  Warning (emacs): 3:: current-column = 0
  ■  Warning (emacs): redisplayed
  ■  Warning (emacs): 4:: current-column = 0
  ■  Warning (emacs): Enabled visible mode
  ■  Warning (emacs): 5:: current-column = 50
  ■  Warning (emacs): redisplayed
  ■  Warning (emacs): 6:: current-column = 50

on my system which seems to be different from what you described.

And for the fun of it: With (indent-tabs-mode -1) tests 3 and 4 report 
column 54 for "5::" and "6::".



  parent reply	other threads:[~2023-07-20 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 20:34 [BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)] Jens Schmidt
2023-07-18  8:13 ` Ihor Radchenko
2023-07-18 19:55   ` Farblos
2023-07-18 20:53   ` Jens Schmidt
2023-07-19  4:35     ` Ihor Radchenko
2023-07-19  6:53       ` [BUG] Emphasis markers should be considered word constituents (was: [BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)]) Ihor Radchenko
2023-07-19  7:10       ` [BUG] SPACE jumps to tag in header line after hidden emphasis marker [9.7-pre (release_9.6.7-562-g5b6268 @ /home/jschmidt/work/org-mode/lisp/)] Ihor Radchenko
2023-07-19 22:37         ` Jens Schmidt
2023-07-20 20:55   ` Jens Schmidt [this message]
2023-07-21  8:30     ` Ihor Radchenko

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39c22e30-de2c-09cb-091d-d26e83f55436@vodafonemail.de \
    --to=jschmidt4gnu@vodafonemail.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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/org-mode.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).