From: "Mark E. Shoulson" <mark@kli.org>
To: emacs-orgmode@gnu.org
Subject: Re: #+STARTUP: showstars
Date: Fri, 25 May 2012 16:57:00 -0400 [thread overview]
Message-ID: <4FBFF21C.7030508@kli.org> (raw)
In-Reply-To: <5083.1337969806@alphaville>
Enda <enda_k2@yahoo.com> writes:
>>> Otherwise is like in vi, the additional stars (like **, opposed to
>>> <SPACE>*) are too noisy, and since I do not want to see them whether
>>> it is in org-mode or in vi, etc, so I wondered was there a way to have
>>> the file like
>>>
>>> * first level heading
>>> =C2=A0* second level heading
>>> =C2=A0=C2=A0 * third level heading
>>
There seems to be some confusion getting across. As I understand it,
this is what the OP is after:
Problem: doesn't like the look of multiple *s for headline; prefers the
look of hidestars-mode.
Furthermore, hidestars isn't good enough, because Enda wants the file
*really to be like that*, without the stars there at all, so that it
still looks good when being edited in vi or something. It needs to look
like hidestars *all the time*, even outside of org, to avoid seeing the
****s.
OP's requested fix: change the syntax so that a line which begins with N
spaces followed by a star and then more spaces after that acts as if the
N spaces at the beginning were stars. That is, <space><space>*<space>
at the start of the line should be a third-level headline, as if it
started with ***.
OP, please let me know if I'm stating your position correctly.
Problem with requested fix: In addition to being a pretty major change
to start with, it also already conflicts with established usage. A line
that starts with spaces and then a star-space is considered an item in a
plain list. Using *s for plain lists is discouraged, because of the
potential confusion with headlines if there are no spaces before it, but
it is permitted (and if it could have been dropped it would have been
already). So, no, this isn't going to happen.
I _guess_ one could try defining something like a NO-BREAK-SPACE
character to behave like a star at the beginning of the line when it
comes to determining headlines, so you basically have a character that
*looks* blank you can use for the non-final stars, but that would also
be a pretty enormous change and I don't see it looking like a good move
either.
I hope that accurately portrays the request (and responses thereto).
~mark
next prev parent reply other threads:[~2012-05-25 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 16:41 #+STARTUP: showstars Enda
2012-05-25 17:30 ` Nick Dokos
2012-05-25 17:43 ` Enda
2012-05-25 17:52 ` Yagnesh Raghava Yakkala
2012-05-25 18:12 ` #+STARTUP: showstars (#+STARTUP: showlaststar) Enda
2012-05-25 18:16 ` #+STARTUP: showstars Nick Dokos
2012-05-25 18:26 ` #+STARTUP: showstars (#+STARTUP: showlaststar) Enda
2012-05-25 18:36 ` Nick Dokos
2012-05-25 21:21 ` Bastien
2012-05-29 12:19 ` Sebastien Vauban
2012-06-01 4:05 ` Nick Dokos
2012-05-25 20:57 ` Mark E. Shoulson [this message]
2012-05-25 22:08 ` #+STARTUP: showstars Bastien
2012-05-26 7:53 ` Michael Brand
2012-05-26 7:30 ` Michael Brand
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=4FBFF21C.7030508@kli.org \
--to=mark@kli.org \
--cc=emacs-orgmode@gnu.org \
/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).