Rasmus <ras...@gmx.us> writes:
> Eric Abrahamsen <e...@ericabrahamsen.net> writes:
>
>> Eric Abrahamsen <e...@ericabrahamsen.net> writes:
>>
>>> Rasmus <ras...@gmx.us> writes:
>>>
>>>> Kaushal Modi <kaushal.m...@gmail.com> writes:
>>>>
>>>>> On Fri, Dec 15, 2017 at 6:23 AM Rasmus <ras...@gmx.us> wrote:
>>>>>
>>>>>> The only way it’s "bad" is in the sense it limits the flexibility of
>>>>>> snippets, like "<s". As you point out, if I add "<sr" as an "src R"
>>>>>> block
>>>>>> I can no longer have "<s" as plain "src" block.
>>>
>>> I don't see any way around that. Any system that allows string keys of
>>> arbitrary length is going to run into that problem.
>>
>> One possible fix, a bit arbitrary: in the default value, provide <TAB>
>> as an artificial "stop key" in the sub-menus. So "s" starts the "source
>> code" sub-menu, and a <TAB> after that simply inserts "#+begin_src", and
>> leaves point after that.
>
> Yeah, I tried to suggest that earlier (unless I didn’t say it), but I
> might not have expressed the idea in an understandable manner :)
Maybe I missed it!
> I think that would be the best approach, but there’s no infrastructure
> that I know of that does this ATM (but I haven’t had a lot of time lately,
> so my knowledge on this issue is limited!).
Can't we do this with tempo? It will have to be "handmade", not
automatic, but:
'(("s" "Source Code")
("se" "Elisp" "src elisp")
("sp" "Python" "src python")
("TAB" "Empty" "src ")
...etc
("e" "Export Block")
("eh" "HTML" "export html")
("el" "LaTeX" "export latex")
("TAB" "Empty" "export ")
...etc
("v" "Verbatim" "verbatim")
("q" "Quote" "quote")
("E" "Example" "example")
...etc
)
