Jack Kamm writes:
> My main motivation was to use my own display-buffer configuration to
> show the source buffer. So I've rewritten the patch to be smaller and
> more conservative, just adding a "plain" option to org-src-window-setup,
> and not changing the implementation of any existing options
I just thought that practically speaking, I no interpreter should
really need stdin, right?
Since everything that is prepended with a shebang: #! interpreter
is at the same time a valid shell script, isn't it?
сб, 18 янв. 2020 г. в 13:02, Kyle Meyer :
>
> Vladimir Nikishkin writes:
>
> > Is it tr
Samuel Wales writes:
> is isearch intended to be also affected? or just org-next-link? i
> suppose isearch is a generic emacs thing, just as lgrep would be
> generic, and most folk would want it to be generic and would get too
> confused if it were not, but just want to make sure.
No, isearch
This patch fixes several related issues with python blocks with
parameters ":session :results value", including:
- Broken if-else and try-except statements.
- Correctly parsing blank lines in indented blocks.
- Returning the correct value when the underscore "_" variable
has been assigned.
It w
thanks from here too! interesting.
is isearch intended to be also affected? or just org-next-link? i
suppose isearch is a generic emacs thing, just as lgrep would be
generic, and most folk would want it to be generic and would get too
confused if it were not, but just want to make sure.
i hav
Hello Kyle,
> This behavior came up in a previous thread. Quoting Nicolas:
>
> ,[ https://lists.gnu.org/archive/html/emacs-orgmode/2019-04/msg00075.html
> ]
> | This is expected.
> |
> | The value in a properties drawer cannot be a link, even though
> | `org-open-at-point' would normally ope
Hello,
I recently authored an package called "om.el" which is a functional org-mode
API akin to dash.el primarily using org-element. Briefly, it provides a library
of (mostly) pure functions that manipulate the parse tree generated by
org-element.el, and uses this to either edit or query the bu
Hi Pedro,
Pedro R.M. Júnior writes:
> I am testing Emacs 28 (Org 9.3) from the Git repository and I have
> noticed that, compared to version 26.3 (Org 9.1.9), `org-next-link'
> function is skipping links located inside the PROPERTIES drawer.
> [...]
> Let me know if this is an intentional behavi
Hello,
I am testing Emacs 28 (Org 9.3) from the Git repository and I have
noticed that, compared to version 26.3 (Org 9.1.9), `org-next-link'
function is skipping links located inside the PROPERTIES drawer. (I
have not tested version 27.) The same does not happen for the links
outsize drawers or
On Tue, Jan 14, 2020 at 8:20 AM Fraga, Eric wrote:
>
> On Tuesday, 14 Jan 2020 at 07:21, Aaron Jensen wrote:
> > In one of my org files, I will occasionally see src blocks lose their
> > formatting. [...]
> >
> > Is this expected behavior? Is there a way to increase the lookback amount?
>
> I don'
Hi Z,
(replying to the list)
I have put together a simplified function based on the code from
https://medium.com/@lakshminp/publishing-a-book-using-org-mode-9e817a56d144,
which simply exports each top-level header to a plain Markdown file. You
can find it here:
https://gist.github.com/zzamboni/2e
> On Jan 20, 2020, at 2:27 AM, Robert Klein wrote:
>
>
> Hi,
>
> when I use a self-defined macro in a macro definition, subsequent
> macros in the same macro definition don't get expanded (tested with
> org version 9.2.1 and tip of maint):
The expansions in your example follow the rules.
Hi,
when I use a self-defined macro in a macro definition, subsequent
macros in the same macro definition don't get expanded (tested with
org version 9.2.1 and tip of maint):
--- snip example ---
#+Macro: newline (eval "\n")
#+Macro: new $1 {{{newline}}}#+Index: $1 {{{newline}}}
Use the {{{new
13 matches
Mail list logo
