Q: org-publish-project-alist and :exclude

In the Org Mode manual section 14.1.3, it says that ":exclude" takes a regular expression of filenames to exclude from publishing but it doesn't really explain what the regular expression format is (I assume Elisp regex). I have two Org files that I want to exclude: * calendar-beorg.org *

Re: Possible to set block switches "globally"?

> I think that we can take names from the parser internals: I had a similar thought immediately after I sent my previous email. > :number-lines > :preserve-indent > :retain-labels > :use-labels > :label-fmt I thought that we might be able to combine :retain-labels and :use-labels, but now

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

Max Nikulin writes: > Another case: > > (org-babel-read "\"Newlines\"\n" t) > "\"Newlines\" > " https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0227e1260 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

Max Nikulin writes: > you added to tests, does not cause the error since the unbalanced > parenthesis is after first string. With the new regexp the error might > happen for > > (org-babel-read "\"Quoted closing quote:\\\"" t) > > but it is caught by `ignore-errors'. I added this to the

Re: Citations: strip braces {} in titles in bibliographies in basic style?

Ihor Radchenko writes: >> Should they be stripped? I suggest they should. > ... > This is a more difficult problem actually, because Bibtex allows more > than just curly braces - see https://www.bibtex.org/SpecialSymbols/ and > https://www.bibtex.org/Format/. > > I tried to ask for bibtex.el to

Re: [BUG] tracker.orgmode.org does not track anything since March 8, 2024

Ihor Radchenko writes: > Woof! does not seem to update the new emails any more. > https://tracker.orgmode.org/?sorting-by=date page only contains emails > back from March. No new bugs/requests/news are visible. I restarted Woof, let's see if the dog is barking again. -- Bastien Guerry

Re: [PATCH] Add support for shortdoc link type

On 2024-05-04, 14:38 +0700, Max Nikulin wrote: > It is necessary to maintain backward compatibility for `ol-info'. I do > not know what kind of separator was added earlier: "::" or "#". I > suppose, for new link type, rules more close to file: links may be used, see > (info "(org) Search

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

Max Nikulin writes: Quotes are not stripped: On 04/05/2024 18:51, Ihor Radchenko wrote: Fixed, on main. Another case: (org-babel-read "\"Newlines\"\n" t) "\"Newlines\" "

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

On 04/05/2024 18:51, Ihor Radchenko wrote: Max Nikulin writes: Quotes are not stripped: (org-babel-read "\"abc\nsdf\"" t) "\"abc sdf\"" Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=edb5eaaac Thanks (org-babel-read "(\n\"abc\"\n" t) progn: End of file

[BUG] tracker.orgmode.org does not track anything since March 8, 2024 (was: Org site is down)

Bastien Guerry writes: > Ihor Radchenko writes: > >> A few reports showed up in the tracker since my previous email. >> However, not all the reports. >> ... Woof! does not seem to update the new emails any more. https://tracker.orgmode.org/?sorting-by=date page only contains emails back from

Re: [PATCH] copy cell contents to kill-ring. WAS [FR]: thing-at-point 'org-table-cell

Pedro Andres Aranda Gutierrez writes: > I needed this function to copy contents from an org spreadsheet to a Web > page and I see it may be useful to others. Take a look and if you find it > useful, I'll add the changelog stuff. > ... > +(defun org-table-copy-cell-as-kill (verbose) > + "Copy

Re: Possible to set block switches "globally"?

João Pedro writes: >> :number-lines (yes|no|continue) as João proposes >> :indent (preserve|align|???) not sure about naming >> :labels (link|keep|remove|remove-whitespace) >> :label-format regexp-string > > Yeah, as Ihor pointed out I did forget about -i, though I'm not

Re: can clocktable link to IDs?

Bill White writes: > When I create a clocktable, its entries are links to heading text: > > [ [file:/path/to/meetings.org::*featureset meeting][featureset meeting] ] > .. > Is there a way to convince the clocktable mechanism to link to a unique ID > (when it exists) rather than a possibly

Re: [FR] Support headline as a function for file+headline target for org-capture-templates

Nafiz Islam writes: > So far I have written this code... > > (defun org-capture-expand-headline (headline) > "Expand functions, symbols and strings for HEADLINE. > > > When HEADLINE is a function, call it. When it is a form, evaluate > it. When it is a variable, return its value. When it is

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

Max Nikulin writes: >> I do not see why we should limit things to single-line strings. > > Quotes are not stripped: > > (org-babel-read "\"abc\nsdf\"" t) > "\"abc > sdf\"" Fixed, on main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=edb5eaaac > (org-babel-read "(\n\"abc\"\n"

Re: [Q/Bug?] Comment for noweb reference comments content

João Pedro writes: > #+begin_src emacs-lisp :noweb yes :comments noweb :tangle /tmp/foo.el > (progn > <>) > #+end_src > > #+name: foo > #+begin_src emacs-lisp > (message "foo") > #+end_src > ... > ;; [[file:...][No heading:1]] > (progn > ;; [[file:...][foo]] > (message "foo") > ;; foo

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

On 04/05/2024 15:03, Ihor Radchenko wrote: Max Nikulin writes: I have no idea if "other\n\"string\"\nlines" may be passed `org-babel-read', but it is not discarded by the current regexp: "^[[:space:]]*\"\\(.*\\)\"[[:space:]]*$" I do not see why we should limit things to single-line strings.

Re: org-agenda: setting face to an item by its tag/category/property

Ilya Chernyshov writes: > Is there a custom variable in org-agenda that allows to set a specific > face (or just foreground/background) for items with specific > property/tag/category? No.

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

Max Nikulin writes: >>> (org-babel-read "\"1\" 2 \"3\"" t) >>> "1\\" >> >> Fixed, on main. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2028bb15c > > I have no idea if "other\n\"string\"\nlines" may be passed > `org-babel-read', but it is not discarded by the

Re: Importing "quoted" strings in `org-babel-import-elisp-from-file'

On 03/05/2024 19:06, Ihor Radchenko wrote: Max Nikulin writes: What I do not like in `org-babel-read' is false positive for escaped quote when actually backslash is escaped: (org-babel-read "\"1\" 2 \"3\"" t) "1\\" Fixed, on main.

Re: [BUG] Attachments not resolved correctly from symlinked Org files

Karthik Chikmagalur writes: >> I can see the problem. >> But what would you expect to happen if there was no attachment in the >> original directory? Should the attachment be created relative to the >> original file? To the symlink? > > I don't know. I would expect the attachment to always be

Re: [PATCH] Add support for shortdoc link type

On 04/05/2024 04:41, Bruno Cardoso wrote: On 2024-05-02, 17:41 +0700, Max Nikulin wrote: [...] I implemented the search option by borrowing the regexp from `ol-info': It is necessary to maintain backward compatibility for `ol-info'. I do not know what kind of separator was added earlier:

[PATCH] copy cell contents to kill-ring. WAS [FR]: thing-at-point 'org-table-cell

Hi, I needed this function to copy contents from an org spreadsheet to a Web page and I see it may be useful to others. Take a look and if you find it useful, I'll add the changelog stuff. Thanks for the guidance ;-) Best, /PA On Fri, 3 May 2024 at 21:50, Ihor Radchenko wrote: > Pedro Andres

Re: PATCH] Auto-complete PRINT_BIBLIOGRAPHY with a trailing colon

Pedro Andres Aranda Gutierrez writes: >> * lisp/org.el (org-options-keywords): Add a trailing colon to the >> 'PRINT_BIBLIOGRAPHY' keyword to avoid unnecessary user confusion. > > Hi Rudolf, > > I don't see any confusion by not having a trailing colon in > #+print_bibliography. Where would there