From: Kyle Meyer <kyle@kyleam.com>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-capitalize-example-region-markers
Date: Tue, 24 Jan 2017 22:25:04 -0500 [thread overview]
Message-ID: <87r33rn81o.fsf@kyleam.com> (raw)
In-Reply-To: <CAMfbzvD95X=Fg7rUdoJ0nUitvW=zgPgX8C_FwtTXGSKQ1xpxOg@mail.gmail.com> (Vicente Vera's message of "Wed, 25 Jan 2017 02:17:11 +0000")
Vicente Vera <vicentemvp@gmail.com> writes:
> Hello.
>
> Just noticed that example block headings wrapping code evaluation
> results appear downcased (arrows added):
>
> #+RESULTS:
>
> #+begin_example <=
> ... some result...
> #+end_example <=
>
> In ob-core.el, line 2438 there's a "hidden" variable that controls
> wether the headings appear upcased:
> ‘org-babel-capitalize-example-region-markers’. Setting it to non-nil
> seems to solve the "problem".
>
> Shouldn't this variable be public through the customize interface?
Yes, I think it should be. And it would be consistent with
org-babel-results-keyword being a defcustom.
I don't see a reason for making it a defvar given in f64a859db (force
cap of auto-inserted begin/end example block, 2012-05-21), the commit
that introduced the variable [1], or in the post [2] that resulted in
the addition.
> Also, it seems "capitalize" is the wrong verb here?
Something with "upcase" or "uppercase" would have been better given the
behavior of upcase and capitalize.
[1] Originally named org-babel-capitalize-examplize-region-markers
[2] https://lists.gnu.org/archive/html/emacs-orgmode/2012-05/msg00607.html
--
Kyle
next prev parent reply other threads:[~2017-01-25 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 2:17 org-babel-capitalize-example-region-markers Vicente Vera
2017-01-25 3:25 ` Kyle Meyer [this message]
2017-01-25 5:17 ` org-babel-capitalize-example-region-markers Kyle Meyer
2017-01-27 1:12 ` org-babel-capitalize-example-region-markers Kyle Meyer
2017-01-28 2:50 ` org-babel-capitalize-example-region-markers Vicente Vera
2017-02-26 20:20 ` org-babel-capitalize-example-region-markers Sebastien Vauban
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=87r33rn81o.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=vicentemvp@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).