From: Grant Rettke <gcr@wisdomandwonder.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Is <s TAB supposed to expand into upper case #+BEGIN_SRC?
Date: Mon, 9 Jun 2014 16:25:51 -0500 [thread overview]
Message-ID: <CAAjq1mcjyy5gWiyrqnHRpSGkTbn-XDkDftTKcH8zo3UnR8jipQ@mail.gmail.com> (raw)
In-Reply-To: <87mwdmk9bu.fsf@gmail.com>
Understood. Thanks Nick.
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Sun, Jun 8, 2014 at 11:15 PM, Nick Dokos <ndokos@gmail.com> wrote:
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>
>> Hi,
>>
>> When I type
>>
>> <s TAB
>>
>> it is expanded into
>>
>> #+BEGIN_SRC
>>
>> #+END_SRC
>>
>> Is supposed to expand into upper case letters?
>>
>> For some reason, my system won't tangle blocks that are all upper
>> case, instead only all lower case is tangled.
>>
>
> All the discussion has been about changing the expansion to lower case,
> but that misses the point: why does tangling not work? AFAIK, things
> are supposed to work whether or not source blocks are demarcated with
> upper-, lower-, or mixed-case. So if it's not working for you, it's
> either a bug or it's some problem in your setup. Can you please post
> a minimal example so we can try it out and determine whether it is a
> bug?
>
>
> Thanks,
> --
> Nick
>
>
>
prev parent reply other threads:[~2014-06-09 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 19:55 Is <s TAB supposed to expand into upper case #+BEGIN_SRC? Grant Rettke
2014-06-07 20:37 ` Thorsten Jolitz
2014-06-07 20:39 ` Thorsten Jolitz
2014-06-07 21:44 ` Grant Rettke
2014-06-08 20:04 ` Grant Rettke
2014-06-08 21:29 ` Thorsten Jolitz
2014-06-09 0:05 ` Grant Rettke
2014-06-09 4:15 ` Nick Dokos
2014-06-09 21:25 ` Grant Rettke [this message]
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=CAAjq1mcjyy5gWiyrqnHRpSGkTbn-XDkDftTKcH8zo3UnR8jipQ@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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).