From: Amin Bandali <bandali@gnu.org>
To: Gabriele Lana <gabriele.lana@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-tempo violating org-mode conventions since 9.2
Date: Fri, 25 Jan 2019 11:04:28 -0500 [thread overview]
Message-ID: <87pnskiv03.fsf@aminb.org> (raw)
In-Reply-To: <CA+bK9UF9O73Anz8d33+8BGkWjM_ahtNx0nNMa7pB4uJMbCUzCQ@mail.gmail.com> (Gabriele Lana's message of "Fri, 25 Jan 2019 15:05:00 +0100")
On 2019-01-25 3:05 PM, Gabriele Lana wrote:
> Hi,
>
> following the conventions (https://orgmode.org/manual/Conventions.html)
> "Keywords and blocks are written in uppercase to enhance their readability"
> but since 9.2 all blocks inserted are lowercase, why?
>
> Is there a clean way to put them back in uppercase? I mean alse the ~BEGIN~
> and ~END~ part of the blocks
>
Just to throw in my 2¢, I personally strongly prefer the less-obnoxious
all-lowercase variant for all ‘#+’ keywords, though I do sometimes use
uppercase for things like #+TITLE or #+AUTHOR every now and again.
I think it would be nice to provide a defcusom to allow choosing between
upper vs. lowercase. As of now, you should be able to get all uppercase
by customizing the `org-tempo-keywords-alist' list and by redefining
`org-tempo-add-block' (for the “begin” and “end” parts) in org-tempo.el.
>
> Thanks
>
> --
> Gabriele Lana
> https://github.com/gabrielelana
> https://twitter.com/gabrielelana
Best,
amin
next prev parent reply other threads:[~2019-01-25 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 14:05 org-tempo violating org-mode conventions since 9.2 Gabriele Lana
2019-01-25 16:04 ` Amin Bandali [this message]
2019-01-26 8:11 ` Michael Welle
2019-01-26 8:58 ` Tim Cross
2019-01-26 9:47 ` Michael Welle
2019-01-27 2:56 ` stardiviner
2019-01-27 16:24 ` Gabriele Lana
2019-01-25 17:01 ` Nicolas Goaziou
2019-01-27 15:50 ` Gabriele Lana
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=87pnskiv03.fsf@aminb.org \
--to=bandali@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gabriele.lana@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).