From: Ihor Radchenko <yantar92@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: "DEBRY.Edouard" <edouard.debry@mbda-systems.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Orgmode plain list bullet : change automatically with list depth
Date: Fri, 17 Jun 2022 19:54:09 +0800 [thread overview]
Message-ID: <87edznjyji.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8ubNqfMaaVDst_B5CPhBKjqMjrgV6Ff0+JqJvevs-6ryA@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> i wonder if org could do the semantics in the text, while
> fontification could do the appearance only.
>
> org allows you to change the bullet style [real text bullets rather
> than fontification] upon demotion.
>
> thus, you can have it consistent that demoting + from top level will
> create - on level 2 for 1 item. until you change it.
>
> but org does not enforce by level. so you can't keep the results of
> your demotion strategy in the rest of the list. an enforced scheme
> would have it so that a change to new bullet style at a level, or
> level 1 otherwise, would style that level.
Could you please provide an example. I do not understand what you are
trying to suggest.
Best,
Ihor
next prev parent reply other threads:[~2022-06-17 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 15:03 Orgmode plain list bullet : change automatically with list depth DEBRY.Edouard
2022-06-15 4:31 ` Ihor Radchenko
2022-06-16 9:14 ` DEBRY.Edouard
2022-06-16 9:59 ` Ihor Radchenko
2022-06-16 23:26 ` Samuel Wales
2022-06-16 23:27 ` Samuel Wales
2022-06-17 11:54 ` Ihor Radchenko [this message]
2022-06-17 23:27 ` Samuel Wales
2022-06-18 0:17 ` Tim Cross
2022-06-19 13:40 ` Edouard Debry
2022-06-19 22:50 ` Tim Cross
2022-06-19 13:55 ` Edouard Debry
2022-06-19 14:03 ` Ihor Radchenko
2022-06-19 14:49 ` Edouard Debry
2022-06-24 14:28 ` DEBRY.Edouard
2022-06-25 3:27 ` Ihor Radchenko
2022-06-29 12:42 ` DEBRY.Edouard
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=87edznjyji.fsf@localhost \
--to=yantar92@gmail.com \
--cc=edouard.debry@mbda-systems.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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 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.