Re: Org mode "style sheet" for software documentation

Perry Smith writes: >> We currently do not support extensions to emphasis, though we may do it >> in future. See https://orgmode.org/list/87letvrege.fsf@localhost >> >> Implementing new emphasis markers will require introducing a new syntax >> object into org-element.el. Such object will unlikel

Re: Org mode "style sheet" for software documentation

On 08/09/2022 23:20, Perry Smith wrote: I’d like to be able to separate out things like file paths, code samples (both in line and block), keywords, environment variables, code variables, etc. ... It would also help me to be more consistent while I write because I’m (currently) having to reme

Re: Org mode "style sheet" for software documentation

> On Sep 9, 2022, at 00:09, Ihor Radchenko wrote: > > Perry Smith writes: > >> So… it seems I didn’t the two BORDER characters do not need to match. So >> I’m off trying to figure out a way to create more emphasis MARKERS. In the >> old days, we had only about 43 non-alphanumeric characte

Re: Org mode "style sheet" for software documentation

Perry Smith writes: > So… it seems I didn’t the two BORDER characters do not need to match. So I’m > off trying to figure out a way to create more emphasis MARKERS. In the old > days, we had only about 43 non-alphanumeric characters to play with but now > with Emacs being 8 bit clean for cou

Re: Org mode "style sheet" for software documentation

> On Sep 8, 2022, at 11:20, Perry Smith wrote: > > I don’t understand this page: > https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers > > > In particular, the BORDER BODY BORDER part. Note that this is the CONTENT >

Org mode "style sheet" for software documentation

I don’t understand this page: https://orgmode.org/worg/dev/org-syntax.html#Emphasis_Markers In particular, the BORDER BODY BORDER part. Note that this is the CONTENT which is already between MARKERS. What I *think* I want is the