Am Mon, 18 Jan 2021 10:17:11 +0800
schrieb Ihor Radchenko :
> Raoul Comninos writes:
>
> > It works now and its awesome! I cannot believe that they had this
> > feature and removed it. I am a very happy man and I cannot thank
> > you enough.
>
> This feature creates a lot of junk text when
Kevin Foley writes:
> +(`(,_ ,f)
> +(when (listp f)
> + (let ((args (funcall (nth 1 f)))
> +(func (nth 0 f)))
> +(setq f (apply #'apply-partially func args
> +(setq cmd f) (setq redo-at-end t))
That will not
On 05/09/2020 14:52, Bastien wrote:
stardiviner writes:
When I press =[C-u C-u C-c C-o]= to open an image file link with system external
program. It can't open the image file.
I cannot reproduce the problem here.
If you still have this issue, can you provide a minimal reproducible
Kyle Meyer writes:
> I'm okay with the minimal fix to the regexp, though I wonder if we can
> avoid the follow-up call to org-read-date-analyze entirely. I'm running
> out of time to test thoroughly tonight, but perhaps something like this
> (ignoring the potential cond->if cleanup):
Testing
This question is in the context of using Org-id UUIDs for linking between
files. If I understand correctly, Org-id knows where to look for UUIDs
(generated by org-id-get-create) by looking at the org-id-locations
variable. But what if I move an .org file that I've generated a UUID into
another
"Dr. Arne Babenhauserheide" writes:
> You can use <> to make it possible to link to any
> place in a document.
It does not work globally though. One cannot just put
[[id:some-anchor-name]] link in other file.
Best,
Ihor
Maxim, thanks for your detailed explanation.
I confirmed the problem:
#+begin_src emacs-lisp
;;; does not work
(start-process-shell-command "xdg-open" nil "xdg-open
/usr/share/icons/gnome/256x256/actions/stock_print.png")
;;; works fine
(start-process-shell-command "feh" nil "feh
aroz...@gmail.com writes:
> I'm just getting into Emacs/Org-Mode. It's clearly an amazing system and
> the linking via UUID is very useful. My question is: why is linking by UUID
> (and, more generally, the creation of properties drawers) limited to
> headlines, and not to sub-elements like list
On Sun, Jan 17, 2021 at 07:12:21PM -0500, John Kitchin wrote:
> I guess this is what you mean:
>
>
> * heading L1_12
> ** heading L2_37
>
> #+name: this-block
> #+header: :var VAR1=(getenv "HOSTNAME")
> #+header: :var VAR2=(message user-login-name)
[more good stuff elided]
Not the OP here,
