On Fri, Nov 30, 2018 at 11:25 AM Marcin Borkowski wrote:
> On 2018-11-28, at 03:08, Grant Rettke wrote:
> > On Tue, Nov 27, 2018 at 3:57 AM Marcin Borkowski wrote:
> >> but it's fairly complicated. Any better ideas?
> >
> > What is the part that you think is too complicated?
>
> I hoped that I
On 11/21/18, Nicolas Goaziou wrote:
> You can use a zero-width space, like +++.
that trick does not work on ===.
Hi,
I have recutils data base and from that I want to use inline source code
to generate a list of names, addresses, etc. for instance the following
inline code when exported in latex
src_sh[:results raw :results replace :exports results :eval yes]{recsel
-t InterestedParties -e "IPName='Ch
Hello,
I've implemented a new file to contrib/lisp. It's called org-envolve.el,
this file implements functions to help to format in org-mode from
ASCII. For instance, you have a bash source that you are copying in your
buffer, later you can call org-envolve-tags to add #+BEGIN_SRC bash in
the beg
> (when (looking-at "[ \t]*#\\+BEGIN_\\S-+[ \t]+\\(\\S-+\\)")
Sorry, it obviously should have been \\(.+\\) at the end.
One thing the core parser could do is to put the remaining of the
opening line of a special block into an :args or similar property of
the special block element, leavi
> > 1. Allow for special blocks to take an :options argument.
>
> Although I agree that this would be nice, I imagine the difficulty would be
> that it would be difficult to cater for multiple backends.
It's not really difficult, more on the trivial side. For example, as
an end user I already can
On Saturday, 1 Dec 2018 at 13:24, Carlos Pita wrote:
> Now, there are special blocks [1] also, and it's a pity they are not
[...]
> So my request would be:
>
> 1. Allow for special blocks to take an :options argument.
Although I agree that this would be nice, I imagine the difficulty would be
Hi all!
The standard mapping from org structures to beamer structures
introduces boilerplate:
1. At the bare minimum a properties drawer.
2. Then there is the tag.
3. But above all the need to add an ignoreheading subsection (with its
drawer and everything) to introduce a little text between, say
