all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Michal Nazarewicz <mina86@mina86.com>,
	emacs-devel@gnu.org
Subject: Re: [RFC] Add :invisible face attribute
Date: Sat, 21 Dec 2024 18:28:28 +0000	[thread overview]
Message-ID: <87msgoao1f.fsf@localhost> (raw)
In-Reply-To: <81970ad8-d2a4-eca6-d8cd-4092fbbac90d@gmail.com>

Jim Porter <jporterbugs@gmail.com> writes:

> I'm just brainstorming here, but could Org use a display spec with 
> specified spaces[1] to make Emacs render a space of the appropriate 
> width? That requires a bit of computation, but it's how 
> 'visual-wrap-prefix-mode' and SHR handle (roughly) similar sorts of things.

If one uses display spec, editing the text underneath will become
tricky. Org mode is first and foremost a text format and should remain
editable using normal text editing commands.

Of course, third-party packages are free to make such visual changes, if
they believe that they constitute an improvement.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2024-12-21 18:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 16:08 [RFC] Add :invisible face attribute Michal Nazarewicz
2024-12-18 16:52 ` Eli Zaretskii
2024-12-18 18:05   ` Michal Nazarewicz
2024-12-21 17:46   ` Jim Porter
2024-12-21 18:28     ` Ihor Radchenko [this message]
2024-12-21 18:52       ` Jim Porter
2024-12-21  4:51 ` Richard Stallman
2024-12-21 16:09   ` Michal Nazarewicz
2024-12-21 18:05     ` Kévin Le Gouguec
2024-12-21 18: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

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

  git send-email \
    --in-reply-to=87msgoao1f.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=mina86@mina86.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.