[O] Bug: Feature request: make org-link emacs wide mode [9.2.5 (9.2.5-elpa @ /home/data1/protected/.emacs.d/elpa/org-20190801/)]

Emacs : GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2019-08-04 Package: Org mode version 9.2.5 (9.2.5-elpa @ /home/data1/protected/.emacs.d/elpa/org-20190801/) I would like to request feature so that Org Links can be turned on Emacs wide as org-link-mode.

[O] Bug: Feature request: make org-links elisp functions take parameter [9.2.5 (9.2.5-elpa @ /home/data1/protected/.emacs.d/elpa/org-20190801/)]

Emacs : GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2019-08-04 Package: Org mode version 9.2.5 (9.2.5-elpa @ /home/data1/protected/.emacs.d/elpa/org-20190801/) I can see that Hide Org Link Abbrev Alist: can accept emacs lisp function. The function is the

Re: [O] Bug: Feature request: make org-link emacs wide mode [9.2.5 (9.2.5-elpa @ /home/data1/protected/.emacs.d/elpa/org-20190801/)]

> I would like to request feature so that Org Links can be turned on > Emacs wide as org-link-mode. Then links could work in various buffers, > and this could make hyperlinking possible from any kinds of files. For reference: https://github.com/seanohalpin/org-link-minor-mode https://github.com/t

[O] nested plain lists

Hi I know it is possible to have simple, enumerated (and other type of lists), but I can't find information concerning nested lists, such as 1. 1.1. 1.2. Is this possible? Somebody knows about it? Thanks Uwe Brauer

Re: [O] nested plain lists

Hi Uwe, Yes, this is supported and documented: https://orgmode.org/manual/Plain-lists.html For example: 1. Item 1 1. Sub item 1.1 1. Sub-sub item 1.1.1 2. Sub Item 1.2 2. Item 2 1. Sub item 2.1 --Diego On Wed, Aug 7, 2019 at 3:52 PM Uwe Brauer wrote: > > > Hi > > I

Re: [O] getting access to a self-invented option?

On Sat, Aug 3, 2019 at 1:28 AM Thibault Marin wrote: > Hi, > > I am not sure where you are trying to get to the value (in the > publishing function?), but I use something like the following to handle > custom keywords: > > , > | #+MWP_EXPORT_TYPE: slides > | > | #+name: elt > | #+begin_src em

Re: [O] getting access to a self-invented option?

On Sat, Aug 3, 2019 at 1:42 PM Berry, Charles wrote: > Matt, > > This seems like a good use case for a `derived-backend'. > > You can use `org-export-define-derived-backend' with 'hugo as the parent, > define a :menu-entry to add an export action for your custom export to the > hugo menu using '

Re: [O] getting access to a self-invented option?

On Fri, Aug 2, 2019 at 4:02 PM Tim Cross wrote: > > Could you just use a tag for this? My shallow thought is that if you > tagged headlines, over time you could use different tags for different > content type whereas if you use a new custom type, you would need to > repeat the definition process

Re: [O] nested plain lists

>>> "DZ" == Diego Zamboni writes: > Hi Uwe, > Yes, this is supported and documented: > https://orgmode.org/manual/Plain-lists.html > For example: > 1. Item 1 > 1. Sub item 1.1 >1. Sub-sub item 1.1.1 > 2. Sub Item 1.2 > 2. Item 2 > 1. Sub

Re: [O] getting access to a self-invented option?

Matt, See inline. > On Aug 7, 2019, at 8:36 AM, Matt Price wrote > > > On Sat, Aug 3, 2019 at 1:42 PM Berry, Charles wrote: > Matt, > > This seems like a good use case for a `derived-backend'. > > You can use `org-export-define-derived-backend' with 'hugo as the parent, > define a :menu-e

Re: [O] getting access to a self-invented option?

Correction below. [snip] > >> >> I guess another option is to just set a buffer-local variable in the file, >> or use #+FILETAGS: and hack htings that way. I'm not sure what the most >> sustainable & org-like method relaly is... >> > > The obvious choice for a local file setting is an OP