emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-tempo and <q TAB with babel headers
Date: Mon, 29 Jun 2020 17:40:23 -0700	[thread overview]
Message-ID: <CAJcAo8uXG--7jOsDjvLxntWntDMge37F+YRR52mgFHZv9B9kGA@mail.gmail.com> (raw)
In-Reply-To: <87imf9ct7i.fsf@kyleam.com>

thank you.

it does work, if you get rid of your entire alist first.  that is, it
doesn't just seem to look up the car and expand it, but rather seems
to require the whole list to be what it wants.

so you cannot fix one at a time.  i tried to fix one at a time because
i wasn't sure which mechanism i would use and what syntax each
mechanism required.

the < mechanism being the same syntax in org but a different syntax in
the alist threw me off ever so slightly.  seems to be backward
compatible for the expansion, but not for the alist.

i didn't think to null the alist until much later when i found out
from you that the syntax i had tried was supposed to work after all.

i also got a capture bug.  the offending item was this one: (push
'("n" "#+name: ?" "") org-structure-template-alist).  therefore the
old syntax.

so no need to fix the bug i guess, but for curiosity here is the bt.

the strange thing is the capture template doesn't expand anything so
idk why it errors just because the expansion mechanism used the old
syntax.  this one might throw others off, dunno.

Debugger entered--Lisp error: (error "Capture abort: Wrong type
argument: stringp, (\"#+name: ?\" \"\")")
  signal(error ("Capture abort: Wrong type argument: stringp,
(\"#+name: ?\" \"\")"))
  error("Capture abort: %s" "Wrong type argument: stringp, (\"#+name:
?\" \"\")")
  org-capture(nil "n")
  #[0 "\300\301\302\"\207" [org-capture nil "n"] 3 nil nil]()
  funcall-interactively(#[0 "\300\301\302\"\207" [org-capture nil "n"]
3 nil nil])
  call-interactively(#[0 "\300\301\302\"\207" [org-capture nil "n"] 3
nil nil] nil nil)
  command-execute(#[0 "\300\301\302\"\207" [org-capture nil "n"] 3 nil nil])

so, user error, plus some anomaly.

however, if any ignorami like me exist out there, it might be worth
documenting int he warning screen that you should null the alist.

On 6/29/20, Kyle Meyer <kyle@kyleam.com> wrote:
> Samuel Wales writes:
>> On 6/29/20, Kyle Meyer <kyle@kyleam.com> wrote:
>>> would map to this (untested):
>>>     ("b" . "src sh :results verbatim output")
>> thanks.  i tried that too.  it gave an error so i assumed it was
>> invalid syntax.  should i report it as a bug?
> Yes, please provide a minimal configuration, the steps to trigger, and
> the error you see.  With maint (currently 3ed035ce3) checked out, I just
> tried
>     (require 'org-tempo)
>     (add-to-list 'org-structure-template-alist
>                  '("b" . "src sh :results verbatim output"))
> with no other configuration.  Both <b followed by tab and "C-c C-, b"
> inserted the block without an error.

The Kafka Pandemic

What is misopathy?

      reply	other threads:[~2020-06-30  0:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 20:15 org-tempo and <q TAB with babel headers Samuel Wales
2020-06-29 20:22 ` tomas
2020-06-29 21:40   ` Samuel Wales
2020-06-29 21:41     ` Samuel Wales
2020-06-29 23:37 ` Kyle Meyer
2020-06-29 23:52   ` Samuel Wales
2020-06-30  0:06     ` Kyle Meyer
2020-06-30  0:40       ` Samuel Wales [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:

  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=CAJcAo8uXG--7jOsDjvLxntWntDMge37F+YRR52mgFHZv9B9kGA@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \


* 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


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).