From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "James R Miller" <james.ryland.miller@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-list: Add back fancy description list indentation
Date: Mon, 18 May 2020 09:06:48 +0200 [thread overview]
Message-ID: <87o8qlsovr.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <b91ae30f-188c-48dc-a07c-dc8f299fa6a6@www.fastmail.com> (James R. Miller's message of "Sun, 17 May 2020 23:23:23 -0500")
Hello,
"James R Miller" <james.ryland.miller@gmail.com> writes:
> Was there really not a way to keep fancy description list indentation
> instead of removing it entirely?
I don't know if there is a way, but the implementation did not work with
nested lists.
> I have almost a decade of org files
> that use description lists,
Note that the removal does not break existing documents.
> and it really helps have the description
> items called out from the description text.
The Org manual contains many descriptions lists.
For short descriptions,
- XXX XXX XXX :: aaaa aaaa aaa aaaaa aaaaa
For longer descriptions,
- XXXXX XXX XXX ::
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
eiusmod tempor incididunt ut labore et dolore magna aliqua.
It doesn't look so bad, IMO. And it is very stable.
> Is there a simple way to add this functionality back in? Perhaps as
> some sort of variable like
> `org-use-fancy-description-list-indentation` instead of throwing it
> out entirely?
It's not just about introducing a variable. It is about fixing
indentation with description lists containing sub-lists.
You can try, if you want to. It may be tricky though: at first glance,
the previous implementation worked, but it actually didn't.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-05-18 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 4:23 Org-list: Add back fancy description list indentation James R Miller
2020-05-18 6:52 ` Colin Baxter
2020-05-18 7:06 ` Nicolas Goaziou [this message]
2020-05-18 14:30 ` James R Miller
2020-05-18 16:12 ` Nicolas Goaziou
2020-05-18 18:57 ` James R Miller
2020-05-19 14:28 ` Nicolas Goaziou
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=87o8qlsovr.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=james.ryland.miller@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/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).