Re: Incorrect quantity of en-spaces

> This appears to be a special case, not documented on org-syntax page. Sounds good, thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Comments following not-really-affiliated keywords are becoming paragraphs

Thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Incorrect quantity of en-spaces

d because "F" is neither the end of the line nor a non-alphabetic character, so we can only match the first two spaces as NAME. emacs version: 29.1 org-mode version: 9bbc21df84d507e568a3ebd17e105cdb9e163784 (latest in git) -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Clock becomes a paragraph by prefixing with not-really-affiliated-keyword

Thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Clock becomes a paragraph by prefixing with not-really-affiliated-keyword

This test document correctly parses as a clock: ``` CLOCK: [2023-04-21 Fri 19:43] ``` This test document incorrectly parses as a paragraph: ``` #+NAME: foo CLOCK: [2023-04-21 Fri 19:43] ``` -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Keyword becoming a paragraph based on optval

> Note that _affiliated keyword_ has an optional form of Ah, that was what I was missing, thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Keyword becoming a paragraph based on optval

Emacs version: 29.1 Org-mode version: f3de4c3e041e0ea825b5b512dc0db37c78b7909e (latest in git) This test document parses as a keyword: ``` #+CAPTION[*foo*]: baz ``` but this test document parses as a paragraph: ``` #+CAPTION[*foo* bar]: baz ``` -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Comments following not-really-affiliated keywords are becoming paragraphs

filiated keyword. [1] https://orgmode.org/worg/org-syntax.html#Keywords -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Org-mode starting with 37d6bde27 errors out parsing org-mode/testing/examples/pub/a.org

nput/home/talexander/git/org-mode/testing/examples/pub/a.org\")\n (org-mode)\n (message \"%s\" (pp-to-string (org-element-parse-buffer)))\n)")) command-line() normal-top-level() Symbol’s function definition is void: org-export--list-bound-variables ``` -- Tom Alexander pgp: https://fizz.buzz/pgp.asc Dockerfile Description: Binary data

Document-level properties incorrect and/or missing based on preceding blank lines and/or comments

nil :CATEGORY nil) ``` Looking farther down the AST it seems the property-drawer became a regular drawer [1] https://orgmode.org/worg/org-syntax.html#Property_Drawers -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Inconsistent text markup handling when double-nesting markers

> Fixed, on main. Thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter

ent they open, but if they open a new document then I would have it auto-insert `#+STARTUP: odd` at the top of the fresh document. Otherwise it seems like org-mode is unsuitable for multi-person collaboration without dictating the contents of everyone's `.emacs` file. -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Inconsistent text markup handling when double-nesting markers

derscore as closing the underline, but that would be invalid because underscore is not a valid POST character and invalid copies of the closing marker are ignored as proven by both "**foo**" and "*foo*bar*". [1] https://orgmode.org/worg/org-syntax.html#Emphasis_Markers [2] https://git.sr

Re: Clarify that REST is not supported on the start TIME in a time-range timestamp.

> As for the problem with REST you raised, I am inclined to remove it from > syntax doc for the time being - it only creates more confusion, > unfortunately. Makes sense, thanks. Is there anything we do to mark patches as rejected? I removed [PATCH] from the subject line. -- Tom Alex

Re: Lesser blocks allowing unescaped lines

Thank you! Makes sense. -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: [PATCH] Clarify that REST is not supported on the start TIME in a time-range timestamp.

REST needs to be separated from TIME? [1] https://github.com/howardabrams/pdx-emacs-hackers/blob/bfb7bd640fdf0ce3def21f9fc591ed35d776b26d/workshops/org-mode-gtd-feature-demo.org#L183 [2] https://orgmode.org/worg/org-syntax.html#Timestamps -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

[PATCH] Clarify that REST is not supported on the start TIME in a time-range timestamp.

. The second line parses as a single timestamp at 8:15. -- Tom Alexander pgp: https://fizz.buzz/pgp.asc From b1114e983d961d48e1d837b8d2ad209a976a5417 Mon Sep 17 00:00:00 2001 From: Tom Alexander Date: Mon, 2 Oct 2023 17:35:28 -0400 Subject: [PATCH] * org-syntax.org (Timestamps): Clarify that REST

Re: Extra paragraphs incorrectly spawning when ":end:" appears.

Hmm thanks, that makes sense. I guess a post-processing step to merge adjacent paragraphs wouldn't work either since that wouldn't stitch together objects like the bold in this test document without re-parsing the entire paragraph: ``` foo *bar :end: baz* ``` oh well 路 -- Tom Alexander pgp

Re: Extra paragraphs incorrectly spawning when ":end:" appears.

Same problem occurs with this sample document: ``` foo #+BEGIN: bar baz ``` which parses as: ``` (section (paragraph "foo\n") (paragraph "#+BEGIN: bar\nbaz\n) ) ``` again, no blank lines and no non-paragraph elements but the single paragraph got split in two. -- Tom Alexa

Extra paragraphs incorrectly spawning when ":end:" appears.

) (paragraph ":end:\nbaz\n") ) ``` The paragraph documentation[1] states that: > Empty lines and other elements end paragraphs. But the document contains no empty lines and we can see in the output that it only contains paragraphs. [1] https://orgmode.org/worg/org-syntax.html#Paragr

Lesser blocks allowing unescaped lines

ines with an unescaped "*" do break up the lesser block: ``` * foo #+begin_src text * bar #+end_src ``` [1] https://orgmode.org/worg/org-syntax.html#Blocks -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

COUNTER-SET for alphabetical ordered lists ignored for utf-8 exporter

/org-syntax.html#Items Emacs 29.1, Org-mode version 9.7-pre (release_9.6.8-781-gc70354) -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Subscript with parenthesis

> Not true. I tried > > b^(*asd*) and bold inside superscript does get parsed. Ah thanks for double-checking! You're right, that is getting parsed. Not sure what test document I was using to make me think objects didn't work inside the parenthesis. -- Tom Alexander pgp: https://

Re: [PATCH] Add backslash to list of POST characters for text markup

Thanks! -- Tom Alexander pgp: https://fizz.buzz/pgp.asc On Fri, Sep 22, 2023, at 5:29 AM, Ihor Radchenko wrote: > "Tom Alexander" writes: > >> Backslash appears to be supported. To test I used the following test >> document: >> ``` >> foo ~bar~\

[PATCH] Add backslash to list of POST characters for text markup

ince that is not a supported POST character, to make sure backslash was not simply escaping the next character. In the documentation I wrote out the word "backslash" in parenthesis to disambiguate between backslash and escaping the following comma. Patch is attached. -- Tom Alexan

Consecutive plain list items of different types

with 3 items: ``` 1. foo - bar - lorem :: ipsum ``` [1] https://orgmode.org/worg/org-syntax.html#Plain_Lists -- Tom Alexander pgp: https://fizz.buzz/pgp.asc

Re: Subscript with parenthesis

that the parenthesis are balanced because this test document does NOT contain a subscript: ``` foo_(b(ar) ``` which is closer to the curly braces requirement since that seems to be the only part of the subscript/superscript documentation that mentions needing balance. -- Tom Alexander

Subscript with parenthesis

meric characters, commas, backslashes, and dots" But I'm seeing the following test document parse as containing a subscript despite using parenthesis which I do not think matches any of the above criteria: ``` foo_(bar) ``` [1] https://orgmode.org/worg/org-syntax.html#Subscript_and_Superscri

Re: Fixed width areas not allowing tab after leading colon.

Thanks! -- Tom Alexander On Sun, Sep 17, 2023, at 5:48 AM, Ihor Radchenko wrote: > "Tom Alexander" writes: > >> The documentation for fixed width areas states: A “fixed-width line” starts >> with a colon character (:) and either a whitespace character or the

Re: [PATCH] Re: Description list with " :: " in the tag.

Sorry for the delay, I've been busy in the IRLs. I've updated the patch to reflect that the parser grabs the text before the last " :: " and then parses it as objects. The new patch is attached. -- Tom Alexander On Thu, Sep 14, 2023, at 7:24 AM, Ihor Radchenko wrote: > "Tom

Fixed width areas not allowing tab after leading colon.

de version: c703541ffcc14965e3567f928de1683a1c1e33f6 (latest in git) Fixed-width area documentation: https://orgmode.org/worg/org-syntax.html#Fixed_Width_Areas -- Tom Alexander

Re: Description list with " :: " in the tag.

I've written a patch (attached) with my proposed wording changes to the documentation, should I be starting another thread or does dropping it here work best? I do not have commit access so I'd need someone with such authority to do the last bit. -- Tom Alexander From

Re: Description list with " :: " in the tag.

Thanks! -- Tom Alexander On Sat, Sep 9, 2023, at 5:06 AM, Ihor Radchenko wrote: > "Tom Alexander" writes: > >> Emacs version: 29.1 >> Org-mode version: 163bafb43dcc2bc94a2c7ccaa77d3d1dd488f1af >> >> Found a conflict between the documentation a

Description list with " :: " in the tag.

)) ``` It seems that "TAG-TEXT" is not just text but it can include objects and those objects can include the substring " :: ". [1] https://orgmode.org/worg/org-syntax.html#Items -- Tom Alexander

Text markup and TeX-style LaTeX fragments spanning more than three lines

lines. foo bar* baz foo *bar \\ baz \\ lorem \\ ipsum \\ dolar* cat ``` Test document TeX-style LaTeX fragments: ``` $foo bar baz lorem ipsum dolar$ ``` -- Tom Alexander

Re: Clarification on blank lines following list items

Thanks! -- Tom Alexander On Tue, Aug 22, 2023, at 4:26 AM, Ihor Radchenko wrote: > Ihor Radchenko writes: > >>> I am seeing dual-ownership of the post-blank in the examples below, but at >>> the same time if I put a plain-list inside a footnote definition, the >>

Re: Clarification on blank lines following list items

agraph: post-blank 0 ``` I re-did both test cases using greater blocks and lesser blocks instead of paragraphs to make sure it wasn't that historical exception at the end of your email, and the post-blank behavior was exactly the same. -- Tom Alexander

Clarification on blank lines following list items

| Yes | Final element of non-final list item | | dog | No| Final list item and not contained in a list item | -- Tom Alexander

Re: Export snippet matching without closing "@@"

> Thanks for reporting! > Fixed, on main. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=e340dde63 Thanks for fixing! -- Tom Alexander

Export snippet matching without closing "@@"

#2))) (paragraph (:begin 68 :end 71 :contents-begin 68 :contents-end 71 :post-blank 0 :post-affiliated 68 :mode nil :granularity nil :parent #1) #("@@\n" 0 3 (:parent #2) ``` -- Tom Alexander

Re: Seemingly inconsistent whitespace ownership

On August 11, 2023 5:20:08 AM EDT, Ihor Radchenko wrote: >"Tom Alexander" writes: > >> The org-mode documentation states: "With the exception of list items, blank >> lines belong to the preceding element with the narrowest possible scope. For >> exam

Seemingly inconsistent whitespace ownership

-blank 4 :post-affiliated 38 :mode planning :granularity nil :parent #2) #("alpha\n" 0 6 (:parent #3))) (paragraph (:begin 48 :end 53 :contents-begin 48 :contents-end 53 :post-blank 0 :post-affiliated 48 :mode nil :granularity nil :parent #2) #("beta\n" 0 5 (:parent #3)) ``` -- Tom Alexander

Re: Documentation: Equal sign incorrectly listed as disallowed in plain links

Thanks for fixing all the documentation issues I submitted today! On Sat, Jul 22, 2023, at 2:58 AM, Ihor Radchenko wrote: > "Tom Alexander" writes: > >> The documentation for plain links states that PATHPLAIN is: >> >>> A string containing non-whites

Documentation: incorrect character name in line breaks

The documentation for line breaks says that PRE is: > Anything but backspace (`\`). I suspect this is supposed to say "backslash" (ascii 92) not "backspace" (ascii 8) Link to the documentation: https://orgmode.org/worg/org-syntax.html#Line_Breaks

Documentation: Equal sign incorrectly listed as disallowed in plain links

The documentation for plain links states that PATHPLAIN is: > A string containing non-whitespace non-bracket (()[]<>=) characters, > optionally containing parenthesis-wrapped non-whitespace non-bracket > substrings up to a depth of two. The string must end with either a > non-punctation

Documentation: Reference to BODY field that is not specified in the grammar

The documentation for Inline Babel Calls mentions that opening and closing square brackets must be balanced within BODY but the grammar above it only defines NAME, ARGUMENTS, HEADER1, and HEADER2. Link to the documentation: https://orgmode.org/worg/org-syntax.html#Inline_Babel_Calls

Documentation: Reference to "KEYCITES" field that is not specified in grammar

The documentation for Citations when specifying which syntactic elements have spaces between them references a "KEYCITES" syntactic element that does not appear anywhere else on the page. Link to the documentation issue: https://orgmode.org/worg/org-syntax.html#Citations

Bug: Inconsistent formatting when terminating bold inside a link [9.3 (release_9.3 @ /usr/share/emacs/27.0.91/lisp/org/)]

L)"]) ("help" :follow org-link--open-help) ("file" :complete org-link-complete-file) ("elisp" :follow org-link--open-elisp) ("doi" :follow org-link--open-doi)) org-latex-format-headline-function 'org-latex-format-headline-default-function org-link-elisp-confirm-function 'yes-or-no-p org-latex-format-inlinetask-function 'org-latex-format-inlinetask-default-function org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"] org-html-format-headline-function 'org-html-format-headline-default-function ) -- Tom Alexander

Re: [O] O[PATCH] org-export-generic table exporting

. On Wed, Feb 15, 2012 at 5:55 PM, Wes Hardaker wjhns...@hardakers.netwrote: On Tue, 7 Feb 2012 23:44:42 -0500, Tom Alexander tomalexan...@paphus.com said: TA I noticed that the org-export-generic.el script had options for basic TA features like checkboxes but not for tables, which were

[O] [PATCH] org-export-generic table exporting

etiquette I might have broken. -- Tom Alexander HS - Secretary Alpha Sigma Phi; Beta Psi Chapter Rensselaer Polytechnic Institute Class of 2013 From 6e072d97d056cb61fc7810b8b9fea43d3cf9489e Mon Sep 17 00:00:00 2001 From: Tom Alexander craftkil...@gmail.com Date: Tue, 7 Feb 2012 20:15:29 -0500 Subject