Re: Automatically use Heading Content as EXPORT_FILE_NAME?
fwiw, what i do is export to a buffer, then write to a file whose name is derived from the header. (alpha-make-valid-path (with-current-buffer org-buffer (org-get-heading 'no-tags 'no-todo))) (defun alpha-make-valid-path (s) "Make a string into a filesystem path." ;; see files.el for this and tramp (subst-char-in-string ?/ ?! (replace-regexp-in-string "!" "!!" s))) i think it might have some issues with long headers and some basename limit on linux. you seem to truncate for that. On 4/26/22, Tim Visher wrote: > On Tue, Apr 26, 2022 at 11:54 AM Tim Visher wrote: > >> I'm currently going to hack around it I think by simply making a function >> that updates the EXPORT_FILE_NAME property with the current heading text. >> > > That's something like > > ``` > (defun timvisher-org-set-export_file_name-property-to-heading-text > () > (interactive) > (org-set-property >"EXPORT_FILE_NAME" >(let ((stripped-heading > (replace-regexp-in-string >"[^-A-Za-z0-9_.~#+ ]" >"" >(substring-no-properties (org-get-heading t t t t) > (substring-no-properties > stripped-heading > 0 > (min (length stripped-heading) 250) > ``` > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com
Re: Automatically use Heading Content as EXPORT_FILE_NAME?
On Tue, Apr 26, 2022 at 11:54 AM Tim Visher wrote: > I'm currently going to hack around it I think by simply making a function > that updates the EXPORT_FILE_NAME property with the current heading text. > That's something like ``` (defun timvisher-org-set-export_file_name-property-to-heading-text () (interactive) (org-set-property "EXPORT_FILE_NAME" (let ((stripped-heading (replace-regexp-in-string "[^-A-Za-z0-9_.~#+ ]" "" (substring-no-properties (org-get-heading t t t t) (substring-no-properties stripped-heading 0 (min (length stripped-heading) 250) ```
Automatically use Heading Content as EXPORT_FILE_NAME?
Hello Everyone, Is there a way to automatically use the text content of the current Heading as the EXPORT_FILE_NAME? AFAICT there isn't. I tend to do most of my Org writing in a few 'mono files' (like todo.org or wiki.org). I then set my export options to default to subtree and visible contents etc. The resulting file is always named after the whole mono file though. Given my usage pattern it would be awesome if it instead could default to the current heading text. Is that something others would be interested in? I'm currently going to hack around it I think by simply making a function that updates the EXPORT_FILE_NAME property with the current heading text. Thanks in advance! -- In Christ, Timmy V. https://blog.twonegatives.com http://five.sentenc.es