Thanks for the feedback. As to the question, what is scatter-gather? --
It's the idea of gathering up scattered pieces of text and consolidating
them in another place, whether elsewhere in the same buffer or
in another file.
Using tags would work, and I've done something similar in my home-brew
On April 1, 2017 10:57:41 PM GMT+05:30, Bob Newell
wrote:
>Org-mode has nearly everything that other outlining tools have, and
>generally much, much more. But one thing that is missing (and
>there's been sporadic traffic about this) is convenient
>scatter-gather.
You don't need those temporary marks I think. Just store the positions in a
variable or use overlays or text properties. You could even make a speed
key to run the mark command.
It could be implemented from a helm command pretty easily too. You can
easily make multiple selections with helm.
Hi,
after the upgrade (require 'org-ref) results in the error message:
(error "Required feature ‘let-alist’ was not provided“)
I am using Aquamacs 3.3 GNU Emacs 25.1.1. I looked for let-plist using
list-packages and found:
let-alist 1.0.4 built-in
What is going wrong?
Org-mode has nearly everything that other outlining tools have, and
generally much, much more. But one thing that is missing (and
there's been sporadic traffic about this) is convenient
scatter-gather. BrainStorm WFO has this; it's not like I'm going to
start using it as an alternative, but such a
Hi.
My computer is running Mac OS, I would like to run some C code from my
VPS which is running GNU/Linux Ubuntu. For example,
#+BEGIN_SRC C :dir /ssh:xuchunyang.me:
puts("Hello, World!");
#+END_SRC
but when I execute this code block with C-c C-c, it popups *Org-Babel
Error Output* and here is
Hi.
I notice that if the result is nil during executing emacs-lisp code
block, org simply displays a empty #+RESULT block. For example,
#+BEGIN_SRC emacs-lisp
t
#+END_SRC
#+RESULTS:
: t
#+BEGIN_SRC emacs-lisp
nil
#+END_SRC
#+RESULTS:
I don't see why 'nil' is special than other values like
Hello,
Carsten Dominik writes:
> but I think the entire url quoting scheme in Org might deserve another
> look.
It does. I also suggested to think about it some time ago.
Ideally, Org should never quote any URI whatsoever. This is really the
root of all evil, because you never
I can confirm the issue appears with those two commands. I forwarded
this report to the Emacs bug tracker.
Regards,
Nicolas Goaziou writes:
> Hello,
>
> Thibault Polge writes:
>
>> With visual-line-mode and org-indent-mode activated, C-a and C-e
>> misbehaves on indented text
Hi everyone, thank you for your input. Matt, thanks a lot for the detailed
look into this. Indeed there are inconsistencies on how this works in Org,
and there are things happening that are system dependent. I thibk what is
biting me this time is the system dependence which is really weird.
Hello,
Alex Branham writes:
> In the latest org release (9.0.5), I get errors when trying to save a buffer
> while editing inside a babel source block. I can reproduce this using Emacs
> 25.1 and 25.2rc2.
>
> Using:
>
> emacs -Q -l ~/org-debug.el
>
> where org-debug.el
Hello,
Francesco Montanari writes:
> When converting ORG to MAN pages (org-man-export-to-man), a new line
> should be added before the line break `.br' tag. Otherwise, for
> example, the following:
> ```
> hello\\
> word
> ```
> is converted to:
> ```
>
Hello,
Mark Meyer writes:
> In ox-epub I'm using several references to external stylesheets,
> starting with the external name in the user filesystem I transform
> these into a kind-of unique id that lives in the EPUB zip file.
>
> Currently I'm doing this using a counter,
Hello,
Thibault Polge writes:
> With visual-line-mode and org-indent-mode activated, C-a and C-e
> misbehaves on indented text blocks. C-a and C-e sometimes start jumping
> over lines (ie, go backwards or forward one extra line) and sometimes
> even reverses direction (C-e
14 matches
Mail list logo