From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: larsi@gnus.org, 56837@debbugs.gnu.org
Subject: bug#56837: 28.1.90; `current-indentation' sometimes returns zero inside invisible text
Date: Sat, 30 Jul 2022 16:25:47 +0300 [thread overview]
Message-ID: <83edy268bo.fsf@gnu.org> (raw)
In-Reply-To: <87ilnerfa9.fsf@localhost> (message from Ihor Radchenko on Sat, 30 Jul 2022 19:49:50 +0800)
> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 56837@debbugs.gnu.org
> Date: Sat, 30 Jul 2022 19:49:50 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> A simpler version would be let-binding buffer-invisibility-spec.
> >
> > Really?
>
> Could you please elaborate? Do I miss something?
Just that I know very well what let-binding does.
The snippet I sent was copy/pasted from the experiments I performed,
it wasn't supposed to be the peak of elegance.
> > These are all display-related, in that their results are supposed to
> > closely reflect what will be shown on display.
>
> I understand. current-column even express it clearly in the docstring
> (unlike, current-indentation). However, as I tried to explain,
> display-independent versions can be useful during parsing. And not only
> in Org mode.
>
> If you think otherwise, we will simply implement the required versions
> in Org.
Let's see what Lars thinks about this.
next prev parent reply other threads:[~2022-07-30 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 7:56 bug#56837: 28.1.90; `current-indentation' sometimes returns zero inside invisible text Ihor Radchenko
2022-07-30 8:51 ` Eli Zaretskii
2022-07-30 9:08 ` Ihor Radchenko
2022-07-30 10:08 ` Eli Zaretskii
2022-07-30 11:27 ` Ihor Radchenko
2022-07-30 11:38 ` Eli Zaretskii
2022-07-30 11:49 ` Ihor Radchenko
2022-07-30 13:25 ` Eli Zaretskii [this message]
2022-07-30 16:35 ` Eli Zaretskii
2022-07-31 8:12 ` 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=83edy268bo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56837@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=yantar92@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).