This message contains my thoughts on a feature request which I think
would be useful: The =:pre= header argument, it would be used to
execute a code block before the code block at point is executed. It
would be similar to the behavior of the =:post= header argument.
Here's a simple example that
Sorry, sending this from the browser because none of Emacs sending options
currently work
From: dalanicolai
To: emacs-orgmode@gnu.org
Subject: Bug: Improve formatting and documentation inline source block [9.3
(release_9.3 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Date: Thu, 18 Feb 2021
Hello,
On 2021-02-18 00:32, Kyle Meyer writes:
>> Looking at the code, I don’t see how it could cause trouble elsewhere
>> (but understanding agenda code is always tricky…)
>
> Yeah, I too think it's safe. If you have the time, I'd appreciate if
> you could skim through the above threads and
Hi,
I would like to propose this (possible) patch.
With `#+STARTUP: macro-arg-sep-other' the macros arguments can be
separated by a string other than comma, whose value is defined in
`org-macro-arg-sep-other' (by default it is "'@").
Rationale for this patch: There are many contexts where the
> From: Maxim Nikulin
> Date: Thu, 18 Feb 2021 19:56:03 +0700
> Cc: 44...@debbugs.gnu.org
>
> I could not estimate effect of such change on windows, so pipe process
> is used only on linux. I am unsure concerning mac however.
On Windows Emacs always uses pipes, because we don't have PTYs there.
Kyle Meyer writes:
> Unrelated note: there's a missing a space between the second "*" and
> "TODO".
Good catch, thank you.
> Perhaps you're not capturing the environment due to your quoting:
>
> ;; -*- lexical-binding: t; -*-
>
> (let ((x 0))
> '(t (lambda () x))) ;; => (y (lambda nil
On Thu, Feb 18, 2021 at 07:10:52PM +0800, Timothy wrote:
>
> Hi Russel,
>
> Russell Adams writes:
>
> > I know I can easily create templates for frequently used code blocks.
> >
> > My question is, is there a completion or in-place documentation for
> > valid header arguments to code blocks? The
On Thu, Feb 18, 2021 at 11:08:32AM +0800, Ihor Radchenko wrote:
> Russell Adams writes:
>
> > I know I can easily create templates for frequently used code blocks.
> >
> > My question is, is there a completion or in-place documentation for
> > valid header arguments to code blocks? The options
On 31/01/2021 23:33, Eli Zaretskii wrote:
From: Maxim Nikulin
Date: Sun, 31 Jan 2021 22:57:57 +0700
Cc: 44...@debbugs.gnu.org
To fix the problem it is better to use (make-process :connection-type
'pipe ...) that unfortunately has no higher level wrappers.
Wouldn't it work to let-bind
Hi,
I’m trying to understand how ob-lilypond handles variables.
I have the following minimal example which compiles correctly:
#+begin_src lilypond :file test.png :cache no
myVar = { e f g}
\relative c' { a b c d \myVar }
#+end_src
Can I move the definition of myVar to a header argument of the
Hi Russel,
Russell Adams writes:
> I know I can easily create templates for frequently used code blocks.
>
> My question is, is there a completion or in-place documentation for
> valid header arguments to code blocks? The options are rather buried
> in the manual.
As it so happens, I have
11 matches
Mail list logo
