Re: [O] Bilingual text in org
> Am 27.11.2017 um 15:16 schrieb Adonay Felipe Nogueira : > > Strange, I might be wrong but this might not be set by default. > > I have Org version 9.1.2 (9.1.2-15.g1d5142, which is of version 20171016 > in GNU Guix package manager). > > Alternatively, per `texdoc babel', you can make the language as a > document class option. You are right, I forgot that option. I have re-added babel to my latex-defaults and added #+LATEX_CLASS_OPTIONS to the file. Thanks for reminding me. Axel
Re: [O] Issue with org git repo and/or worg?
On Thu, Nov 16, 2017 at 9:23 AM Kaushal Modi wrote: > > Shouldn't that commit update this page: > http://orgmode.org/worg/org-blog-wiki.html ? But it hasn't been updated. > >> That page hasn't yet updated. And it looks like worg stopped updating since this commit (the commit prior to mine): http://repo.or.cz/worg.git/commitdiff/0fd04017dc72f15baafed59968ca6f4ba30c26ea Here's the commit log for worg: http://repo.or.cz/worg.git/shortlog (Also copying Matt as he is mentioned here: http://orgmode.org/worg/worg-maintainance.html ) -- Kaushal Modi
Re: [O] Want help for a helper function which send current link file under point to Kindle path.
Does anyone knows how to get the link at the point in Org-mode? For example: Get the "Data/Books/kk.epub" part of [[file:Data/Books/kk.epub][kk.epub]] [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Thu, Jul 13, 2017 at 8:29 AM, numbch...@gmail.com wrote: > I want to write a helper function to send the link file (usually ebooks) > under the point to Kindle path like (/run/media/username/Kindle/ > documents/). > Hope this function can provide the following functionalities: > > - check whether the source file (ebook) exist in Kindle? > - check the source file format, if not Kindle supported, then convert it > with command `ebook-convert` which is comes from program "Calibre". > > I wander how to get the link actual path under the point? > For example, org link like this: > > [[file:Data/Books/kk.epub][kk.epub]] > [[file+sys:/home/username/Documents/kk2.mobi][kk2.mobi]] > > [stardiviner] GPG key ID: 47C32433 > IRC(freeenode): stardiviner Twitter: @numbchild > Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 > Blog: http://stardiviner.github.io/ >
Re: [O] What about a space when inserting a src-block?
+1, aggreed, I wish a better keybinding too. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner Twitter: @numbchild Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 Blog: http://stardiviner.github.io/ On Sat, Dec 2, 2017 at 2:47 AM, Matt Lundin wrote: > Marco Wahl writes: > > > My impression is that one always types a blank after calling > > `org-insert-structure-template' {C-c C-x w s} for creating a src block. > > > > Suggestion: Realize the insert of a space after "#+begin_src" in > > `org-insert-structure-template'. > > > > WDYT? > > +1 > > Also, before this becomes part of an official release, might I also > suggest that we consider changing the default keybinding. I am finding > the "C-c C-x w" binding a bit too close to "C-c C-x C-w," which calls > org-cut-special. I've accidentally lost a couple of subtrees without > noticing. > > Matt > > >
Re: [O] Org mode bug submission and viewing?
TL;DR M-x org-submit-bug-report On Fri, Dec 1, 2017 at 11:05 PM Allen Li wrote: > What's the proper way to submit an Org mode bug, M-x org-submit-bug-report Then follow the prompts.. you will end up with an email message buffer. If your emacs is set up to send emails, just send that email after adding additional information about the bug. Else. copy the body of that email, paste it in your email client (like Gmail, Google Inbox, etc), also copy the auto-generated subject like: Bug: My bug [9.1.3 (release_9.1.3-203-g33d554 @ /home/kmodi/usr_local/apps/6/emacs/emacs-26/share/emacs/site-lisp/org/)] , and send that email to emacs-orgmode@gnu.org. Include a MWE (minimum working example) in your bug report on how to recreate that issue in an emacs -Q session loaded with that specific Org version. and are the bugs > collected anywhere for viewing their status? > I don't believe so. > I see the mailing list has bugs generated using org-submit-bug-report > (containing "Bug:" in the subject) That's generated using the above method. > and other bugs that have numbers ("bug#:" in the subject). > Those are the Org related bugs sent by users using M-x report-emacs-bug. /Those/ get tracked, auto-assigned with a number and you can see those at http://lists.gnu.org/r/bug-gnu-emacs/. > Is there a preferred way to submit bugs? > As a user, and frequent observer of this list, the first method is preferred and gets dealt with in a speedy manner. Because not everyone following the official emacs bug list use Org. Occassionally though, someone would be kind enough to forward Org-related bugs from that list to this list. Where are the numbered bugs coming from? > M-x report-emacs-bug > Is there a place to view submitted bugs and their resolution status? > Not that I know of. This seems to be an unofficial place to list those, and doesn't look updated. -- Kaushal Modi
[O] Org mode bug submission and viewing?
What's the proper way to submit an Org mode bug, and are the bugs collected anywhere for viewing their status? I see the mailing list has bugs generated using org-submit-bug-report (containing "Bug:" in the subject) and other bugs that have numbers ("bug#:" in the subject). Is there a preferred way to submit bugs? Where are the numbered bugs coming from? Is there a place to view submitted bugs and their resolution status?
[O] bug#24791: bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)
On Fri, Dec 1, 2017 at 1:53 PM, Nicolas Goaziou wrote: > Hello, > > Jan Böhm writes: > >> Symptoms: both org-todo-yesterday and org-agenda-todo-yesterday behave >> just like normally setting todo state to "DONE" with org-todo. >> Specifically, the timestamp >> added in the log takes the current time instead of 23:59 of the previous >> day, as would be expected. >> >> Replicate behaviour: >> start emacs -Q >> set org-log-done to "time" >> visit new file and switch to org mode >> create TODO headline and set TODO state to "DONE" by calling >> "org-todo-yesterday" >> ⇒ todo state is set to DONE correctly, but the timestamp inserted in >> the log drawer is the current time. > > I cannot reproduce it in a recent Org release. Could you double-check > with a newer Org? I am going to blindly wager that this is yet another bug caused by Org mode's subtle timezone issues. I can reproduce it (and crucially, I am not in the GMT time zone), although the repro recipe produces a CLOSED timestamp and not a log drawer timestamp.
Re: [O] org to static site?
On 12/01/2017 at 18:19 Adonay Felipe Nogueira writes: > The best approach for me is also to use something such as org-publish, > and a simple static site server such as GNU Serveez. Have you used org-publish in earnest? I settled on the approach used in https://github.com/myglc2/emacsite only after trying out org-publish extensively. I needed source and generated content to sit together in the working tree of complex multi-level reproducible research projects and to be transparently revision controlled and hosted on the organization's Github Entreprise server. After studying both approaches I found the emacsite approach to work better than org-publish. Just to be clear, emacsite does not require GitHub. You can equally well serve the site from the development tree, or you can publish by doing git push to non bare git repos hosted on web servers. In this way emacsite effectively automates site publishing using make and git which I found to be more reliable than org-publish. I also needed to be able to easily preview live results generated on HPC development servers in order to share work in progress with colleges. emacsite supports this natively. A nice lightweight emacs-only way to serve this work is https://github.com/skeeto/emacs-http-server. -George
[O] bug#24791: org-todo-yesterday behaves like plain org-todo (incorrect timestamp)
Hello, Jan Böhm writes: > Symptoms: both org-todo-yesterday and org-agenda-todo-yesterday behave > just like normally setting todo state to "DONE" with org-todo. > Specifically, the timestamp > added in the log takes the current time instead of 23:59 of the previous > day, as would be expected. > > Replicate behaviour: > start emacs -Q > set org-log-done to "time" > visit new file and switch to org mode > create TODO headline and set TODO state to "DONE" by calling > "org-todo-yesterday" > ⇒ todo state is set to DONE correctly, but the timestamp inserted in > the log drawer is the current time. I cannot reproduce it in a recent Org release. Could you double-check with a newer Org? Thank you. Regards, -- Nicolas Goaziou0x80A93738
[O] bug#22469: org-mode export fail
Kyle Meyer writes: > phillip.l...@russet.org.uk (Phillip Lord) writes: > >> Kyle Meyer writes: > > [...] > >>> This should be fixed on the Org side as of 44c8cd7 (2015-08-10): > > [...] > >> Okay. What's the best way to get this fix onto the release branch? > > I'm not sure, but I just asked a related question in bug#22399: > > http://thread.gmane.org/gmane.emacs.bugs/111992 Closing this bug since the issue is solved and the fix landed in Emacs release branch. Regards,
[O] bug#18104: 24.3.92.1; Infloop when capturing Org note
Glenn Morris writes: > PS perhaps this is related to your earlier > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17651 > > Both seem to involve the cache. Closing this. The cache is disabled by default in recent Org releases. Regards,
[O] bug#22798: 25.1.50; org-mode 8.2.10 in core, edit source blocks fails
Nicolas Goaziou writes: > Hello, > > Frank Haun writes: > >> This happens to emacs master. >> >> emacs -Q >> >> For instance ~/tmp/test.org: >> >> #+BEGIN_SRC emacs-lisp >> (setq foo "bar") >> #+END_SRC >> >> Editing this with org-edit-special gives: >> >> Debugger entered--Lisp error: (wrong-type-argument listp t) >> delete((org-filtered) t) >> remove((org-filtered) t) >> org-move-to-column(0) >> org-edit-src-code() >> org-edit-special(nil) >> funcall-interactively(org-edit-special nil) >> call-interactively(org-edit-special nil nil) >> command-execute(org-edit-special) >> >> With org-mode 8.3.3 from Elpa everything is fine. > > 8.2.10, and 8.3.3 are very old releases. I don't think this issue exists > anymore in recent Org. Unless the OP can reproduce the issue in a recent > Org, this bug can be closed. Actually closing this bug. Please re-open a bug if you can reproduce the issue in a newer version of Org. Thank you. Regards,
[O] bug#22777: Can't get Effort and CLOCK properties into the same drawer (PROPERTIES)
Nicolas Goaziou writes: > David Caldwell writes: > >> - org-clock-into-drawer is customized to "PROPERTIES" >> - so both CLOCK and Effort properties should go in the PROPERTIES >> drawer- it works in Org-mode version 8.2.10 (release_8.2.10 @ >> d:/bin/emacs-24.5/share/emacs/24.5/lisp/org/) - result: >> :PROPERTIES: >> CLOCK: [2016-02-22 Mon 15:26] :Effort: 1w :END:- it does *not* >> work in Org-mode version 8.3.3 (8.3.3-55-g9f7d7b-elpa @ >> d:/ddc/.emacs.d/elpa/org-20160215/) >> - result: :PROPERTIES: >> :Effort: 1w :END: :PROPERTIES: CLOCK: [2016-02-22 Mon >> 15:26] :END: > > PROPERTIES is a special, reserved, drawer. You cannot insert anything in > it but node properties. It helps Org finding properties and handling > property inheritance reasonably fast. Closing this bug. Regards,
Re: [O] org to static site?
On 12/01/2017 at 17:17 Tory S. Anderson writes: > I've got a single-chord setup with Hugo, adapted from: > http://www.holgerschurig.de/en/emacs-blog-from-org-to-hugo/ > > I'm very pleased with it. That's cool, but I wanted to avoid "external" components like frameworks, site generators, and themes as much as possible ;-) That's why https://github.com/myglc2/emacsite generates sites directly from org-mode using only emacs and GNU make. The only external component is the Bootstrap javascript front-end library (https://getbootstrap.com) referenced by https://github.com/marsmining/ox-twbs to produce mobile-first sites.
[O] bug#23890: 25.0.94; Org-mode Table does not copy time interval correctly
Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> Hello, >> >> Rares Vernica writes: >> >>> Just to clarify, how would you fix this: >>> >>> | [2016-07-05 Tue]--[2016-07-06 Wed] | 1d | vsum(d) | >>> | [2016-07-06 Wed]--[2016-07-07 Thu] | 1d | 2 d | >>> #+TBLFM: $3=vsum(@1$-1..@0$-1) >>> >>> Notice the "vsum(d)" instead of the expected "1 d". How would you add >>> "identity" here? >> >> You probably need to use Lisp formulas instead of Calc, i.e, wrap the >> formula within '(...). >> >> I'm no specialist about table formulas; I suggest to ask on Org mailing >> list. > > Could this bug be closed? Nevermind. Closing it.
[O] bug#24571: 25.1; OrgMode bug when both a link and tags are in a headline
Nicolas Goaziou writes: > Hello, > > Michael Fiano writes: > >> OrgMode bug when both a link and tags are in a headline >> >> Steps to reproduce: >> >> 1. Start stock emacs: >> $ emacs -Q test.org >> >> 2. Write a headline >> * Test >> >> 3. Issue C-c C-c and the headline to add a tag >> * Test :test: >> >> 4. Modify the headline to include a link. >> * Test [[http://test][test]] :test: >> >> 5. Everything appears to be rendered correctly, but when viewing the >> source, it really looks like: >> [[http://test][te]]st >> >> 6. To make it render wrong and become very obvious, change the link >> description to have multiple words. > > I cannot reproduce it in recent Org release. If the OP cannot either, > I suggest marking this bug as done. Actually closing it. Please re-open a bug if it still fails on a more recent revision. Regards,
[O] bug#19914: 25.0.50; `org-store-link' invokes function to add to `org-store-link-functions' twice
Nicolas Goaziou writes: > Hello, > > Drew Adams writes: > >>> This means that it will have done its thing TWICE: once just to check >>> whether it should/could do its thing and another time so that it does >>> its thing. >> >> Also, the doc of `org-store-link-functions' says nothing about the >> function being called twice. It says only: >> >> "Each function should check if it is responsible for creating >> this link (for example by looking at the major mode). >> If not, it must exit and return nil. >> If yes, it should return a non-nil value after a calling >> `org-store-link-props' with a list of properties and values." >> >> (And "a calling" is a typo - it should be "calling".) >> >> This doc is essentially a spec telling you what a function for this >> list should do. From the doc, its purpose is to (a) check whether >> it should call `org-store-link-props' and (b) if so, call it and >> return non-nil, else return nil (without calling it). >> >> Nothing suggests that the function, if invoked to define a link, >> will be invoked twice: once for (a) (even though (b) will also be >> done then) and a second time for (b). > > This function no longer invokes twice the function used to create the > link. Closing this bug.
Re: [O] org to static site?
The best approach for me is also to use something such as org-publish, and a simple static site server such as GNU Serveez. If you want server-side programming using GNU Guile, dynamic pages or dynamic output/return of .csv/.json files, then the upcomming GNU Artanis might be a good start. I couldn't make use of it yet, but I heard that even GNU Guile has a built-in web server (and if I read all these correctly, GNU Artanis and GNU Serveez only make the usage of this built-in one simpler). Also, in all cases I mentioned you'll be using the already known Scheme language, which is somewhat similar to Emacs Lisp and has more performance than most webserver software today. Also, GNU Artanis allows you to use templates in pages or have a plain HTML page that comes from a mix of HTML and Scheme. 2017-11-30T00:13:12-0500 George myglc2 Clemmer wrote: > On 05/31/2017 at 12:00 Matt Price writes: > > > No doubt too late for your teaching website, but you may find this > interesting ... > > https://github.com/myglc2/emacsite > > HTH - George -- - https://libreplanet.org/wiki/User:Adfeno - Palestrante e consultor sobre /software/ livre (não confundir com gratis). - "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar instantaneamente comigo no endereço abaixo. - Contato: https://libreplanet.org/wiki/User:Adfeno#vCard - Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft Office, MP3, MP4, WMA, WMV. - Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF (apenas sem DRM), PNG, TXT, WEBM.
[O] bug#22798: 25.1.50; org-mode 8.2.10 in core, edit source blocks fails
Hello, Frank Haun writes: > This happens to emacs master. > > emacs -Q > > For instance ~/tmp/test.org: > > #+BEGIN_SRC emacs-lisp > (setq foo "bar") > #+END_SRC > > Editing this with org-edit-special gives: > > Debugger entered--Lisp error: (wrong-type-argument listp t) > delete((org-filtered) t) > remove((org-filtered) t) > org-move-to-column(0) > org-edit-src-code() > org-edit-special(nil) > funcall-interactively(org-edit-special nil) > call-interactively(org-edit-special nil nil) > command-execute(org-edit-special) > > With org-mode 8.3.3 from Elpa everything is fine. 8.2.10, and 8.3.3 are very old releases. I don't think this issue exists anymore in recent Org. Unless the OP can reproduce the issue in a recent Org, this bug can be closed. Regards, -- Nicolas Goaziou0x80A93738
[O] bug#19887: 24.4; Cannot kill buffer; Wrong type argument: overlayp, nil
Hello, Damian Nadales writes: > I must add that I discovered the bug by accident. Normally I don't > change the mode when editing an special org buffer. Since the issue is fixed, I'm closing this bug. Regards, -- Nicolas Goaziou0x80A93738
[O] bug#18870: bug#18870: \emsp and alignment in org clock report
Nicolas Goaziou writes: > Nicolas Goaziou writes: > >> The trick could be to use an Org entity which is as large as its >> overlay. Even better if that entity is readable without that overlay. >> I'll look into it soon. > > This should now be fixed. The markup used is more readable and doesn't > alter table alignment. Could this bug be marked as done? Thank you. Regards,
[O] bug#23890: 25.0.94; Org-mode Table does not copy time interval correctly
Nicolas Goaziou writes: > Hello, > > Rares Vernica writes: > >> Just to clarify, how would you fix this: >> >> | [2016-07-05 Tue]--[2016-07-06 Wed] | 1d | vsum(d) | >> | [2016-07-06 Wed]--[2016-07-07 Thu] | 1d | 2 d | >> #+TBLFM: $3=vsum(@1$-1..@0$-1) >> >> Notice the "vsum(d)" instead of the expected "1 d". How would you add >> "identity" here? > > You probably need to use Lisp formulas instead of Calc, i.e, wrap the > formula within '(...). > > I'm no specialist about table formulas; I suggest to ask on Org mailing > list. Could this bug be closed? Thank you. Regards,
[O] bug#24571: 25.1; OrgMode bug when both a link and tags are in a headline
Hello, Michael Fiano writes: > OrgMode bug when both a link and tags are in a headline > > Steps to reproduce: > > 1. Start stock emacs: > $ emacs -Q test.org > > 2. Write a headline > * Test > > 3. Issue C-c C-c and the headline to add a tag > * Test :test: > > 4. Modify the headline to include a link. > * Test [[http://test][test]] :test: > > 5. Everything appears to be rendered correctly, but when viewing the > source, it really looks like: > [[http://test][te]]st > > 6. To make it render wrong and become very obvious, change the link > description to have multiple words. I cannot reproduce it in recent Org release. If the OP cannot either, I suggest marking this bug as done. Regards, -- Nicolas Goaziou0x80A93738
[O] bug#18870: bug#18870: \emsp and alignment in org clock report
Nicolas Goaziou wrote: > Could this bug be marked as done? Thank you. Anyone can close any bug by sending mail to eg 18870-done at debbugs. (Thanks for looking at these reports.)
[O] Bug in emphasis fontification
Hello, I believe that the recent fontification rules still need tweaking. Here's a MWE: = *bold* = Here's a more detailed version: = *bold* ^ above does not work *bold* this works at the time of typing. But on saving and doing =revert-buffer=, the fontification goes away. This *bold* fontification stays (starting emph char *and* ending emph char not at BOL/EOL). Looks like fontification is lost if emphasis chars are at BOL or EOL. = It looks like this (attached).. notice that the *bold* fontification works only when the emph chars are neither at BOL nor at EOL. The same issue is with all emphasis variants: italics, code, verbatim. -- Kaushal Modi
[O] bug#18870: bug#18870: \emsp and alignment in org clock report
Hello, Glenn Morris writes: > Nicolas Goaziou wrote: > >> Could this bug be marked as done? Thank you. > > Anyone can close any bug by sending mail to eg 18870-done at debbugs. Indeed! Closing it right now. Thank you. > (Thanks for looking at these reports.) (You're welcome.) Regards, -- Nicolas Goaziou0x80A93738
[O] bug#21838: Org Table edits item incorrectly
Hello, Rittwik Chatterjee writes: > Start emacs with `emacs -Q' > Create a Org file `test.org' > > Copy the following table into that file and save. > > |---+-| > | Plugins | How to install | > |---+-| > | Bookmark plus | Create a folder "bookmark-plus" | > | Company-mode | Create a folder "company" | > |---+-| > > Double click on the word `Create' (to select it) in the third row and press > `:'. > > Expected output: > |---+-| > | Plugins | How to install | > |---+-| > | Bookmark plus | Create a folder "bookmark-plus" | > | Company-mode | Create: a folder "company" | > |---+-| > > Actual output: > |---+-| > | Plugins | How to install | > |---+-| > | Bookmark plus | Create a folder "bookmark-plus" | > | Company-mode | | > |---:+-| > > This can be reproduce by pressing any other character keys, ex. a-z, ( { [ > " etc. This issue is fixed in recent Org releases. Closing this bug. Thank you. Regards, -- Nicolas Goaziou0x80A93738
[O] bug#22734: 24.5; do not leave opened org-agenda-files on org-agenda-list, etc.
Nicolas Goaziou writes: > Hello, > > Eli Zaretskii writes: > >>> From: Oleksandr Gavenko >>> Date: Thu, 18 Feb 2016 16:23:05 +0200 >>> >>> TODO.org I visit only via `C-c a a'. But NOTE.org become unmaintainable with >>> size greater then 1 MiB of plain text. > > It would be interesting to see a profile report about this. > >>> But now I have a lot of opened unused .org files after `C-c a a' which I >>> should kill when they appear during buffer switches. >>> >>> The right behavior is to preserve opened only files that already was opened >>> and kill other files. > > AFAICT, Org expects that agenda files are always being visited. This may > be related to speed issues. > > In any case, you could filter out Org files from buffer list (e.g., with > `ido-ignore-buffers' and alike), and use `org-buffer-list' whenever you > need them. Since there is no more answer from the OP, I'm closing this bug. Regards,
Re: [O] Bug: Incorrect visualization of nodes past the second level [9.1.3 (9.1.3-10-gadfbfd-elpa @ ~/.emacs.d/elpa/org-20171127/)]
Hello, cr...@inventati.org writes: > Starting from the third level, nodes are shown with two asterisks less > than expected. Trying to unfold them will actually fold the whole > subtree instead. > > The bug was present even with a clean Emacs configuration and no > packages installed. For the moment, I solved downgrading to > org-20171023. I think this was fixed in 5873d9912145fb19d00cfa47587f8e16c59da56a, 4 days ago. Regards, -- Nicolas Goaziou
[O] bug#22777: Can't get Effort and CLOCK properties into the same drawer (PROPERTIES)
Hello, David Caldwell writes: > - org-clock-into-drawer is customized to "PROPERTIES" > - so both CLOCK and Effort properties should go in the PROPERTIES > drawer- it works in Org-mode version 8.2.10 (release_8.2.10 @ > d:/bin/emacs-24.5/share/emacs/24.5/lisp/org/) - result: > :PROPERTIES: > CLOCK: [2016-02-22 Mon 15:26] :Effort: 1w :END:- it does *not* > work in Org-mode version 8.3.3 (8.3.3-55-g9f7d7b-elpa @ > d:/ddc/.emacs.d/elpa/org-20160215/) > - result: :PROPERTIES: > :Effort: 1w :END: :PROPERTIES: CLOCK: [2016-02-22 Mon > 15:26] :END: PROPERTIES is a special, reserved, drawer. You cannot insert anything in it but node properties. It helps Org finding properties and handling property inheritance reasonably fast. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] What about a space when inserting a src-block?
Marco Wahl writes: > My impression is that one always types a blank after calling > `org-insert-structure-template' {C-c C-x w s} for creating a src block. > > Suggestion: Realize the insert of a space after "#+begin_src" in > `org-insert-structure-template'. > > WDYT? +1 Also, before this becomes part of an official release, might I also suggest that we consider changing the default keybinding. I am finding the "C-c C-x w" binding a bit too close to "C-c C-x C-w," which calls org-cut-special. I've accidentally lost a couple of subtrees without noticing. Matt
[O] bug#19914: 25.0.50; `org-store-link' invokes function to add to `org-store-link-functions' twice
Hello, Drew Adams writes: >> This means that it will have done its thing TWICE: once just to check >> whether it should/could do its thing and another time so that it does >> its thing. > > Also, the doc of `org-store-link-functions' says nothing about the > function being called twice. It says only: > > "Each function should check if it is responsible for creating > this link (for example by looking at the major mode). > If not, it must exit and return nil. > If yes, it should return a non-nil value after a calling > `org-store-link-props' with a list of properties and values." > > (And "a calling" is a typo - it should be "calling".) > > This doc is essentially a spec telling you what a function for this > list should do. From the doc, its purpose is to (a) check whether > it should call `org-store-link-props' and (b) if so, call it and > return non-nil, else return nil (without calling it). > > Nothing suggests that the function, if invoked to define a link, > will be invoked twice: once for (a) (even though (b) will also be > done then) and a second time for (b). This function no longer invokes twice the function used to create the link. Thank you. Regrads, -- Nicolas Goaziou0x80A93738
Re: [O] can't get org-mode noweb tangle to work
On Fri, Nov 24, 2017 at 11:38 PM, Martin Alsinet wrote: > Hello Charlie: > > I have found that I like better to use a combination of tangle and import > instead of noweb syntax. > > #+BEGIN_SRC python :tangle board.py > def init_board(args) > return [[-1 for x in range(3)] for y in range(3)] > #+END_SRC > > #+BEGIN_SRC python > import sys > import os > from board import init_board > > def main(args): > init_board(args) > > if __name__ == "__main__": > main(sys.argv) > #+END_SRC > > Then, you do a *M-x org-babel-tangle* and org will write the first block > into board.py. Then you go into the second block and run it with *C-c C-c* and > it will load the init_board function from the tangled file. > > Writing it this way forces you to modularize your code blocks to be able > to call them from other blocks and you can even build your whole > application tangling the source blocks into files. > > The :noweb syntax seems to me to be a templating solution used for a code > module problem. > It can be if you like that style. You can define re-usable and callable source blocks and tangle them to their own file and to other files, too. For example using the example above you can use both approaches: #+NAME: init #+BEGIN_SRC python :tangle board.py :comments no def init_board(args) return [[-1 for x in range(3)] for y in range(3)] #+END_SRC #+NAME: org_gcr_2017-11-30_mara_1BB0EB7B-1693-458D-B1AD-CE44ED9961C1 #+BEGIN_SRC python :comments no :tangle program.py import sys import os «init» def main(args): init_board(args) if __name__ == "__main__": main(sys.argv) #+END_SRC Calling `org-babel-expand-src-block'
Re: [O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]
Hello, Nathan Aclander writes: > When using lists in org like the following: > > - Item 1 > - Sub-item 1 > - Sub-item 1 > - Item 2 > - Item 3 > > I can shift them left and right using ~org-shiftmetaright~ or > ~org-shiftmetaleft~. > > This also works on the following list: > > - Item 1 > - This is a very long sub-item that is definitely going to be longer > than 80 characters. > - Sub-item 2 > - Item 2 > - Item 3 > > When my cursor is on the second line ( the line that begins with "This > is a very..." I can move the sub-item left and right as expected. > > When my cursor is on the third line ( the line that begins with "than > 80..." I get a message saying: > > "user-error: This command is active in special context like tables, > headlines or items" > > Because this *does* work when my cursor is on the above line, I know org > knows how to handle multi line items. Therefore I think it's a bug that > org doesn't recognize the cursor being inside a list when it is on the second > line of a multi item list. I don't qualify this as a bug. These commands explicitly work when point is at the beginning of an item. Indeed, the sub-item may be arbitrarily large, contain tables... it would be confusing to move the whole sub-list when its structure is out of sight. Regards, -- Nicolas Goaziou
Re: [O] RFC better Unicode support - Unicode Characters causing problems with TAGs etc.
On Fri, Dec 1, 2017 at 2:40 AM, Tim O'Callaghan wrote: > > Also, are other people using Unicode, and if so, how? especially with > visually consistent tables, For some characters you can handle it by using [[http://orgmode.org/manual/Special-symbols.html][Special symbols]] in the tables for example this lines up correctly: | hi | there | a | b | c | |+---+---+---+---| | \laquo{} | \raquo{} | \pi{} | \check{} | | [[http://orgmode.org/worg/org-symbols.html][Here]] are the symbols. You can also list them by calling `org-entities-help'. > does anyone have a a good mono-spaced to recommend? DejaVuSansMono. With Symbola as a fallback: (set-fontset-font "fontset-default" nil (font-spec :size 20 :name "Symbola"))
Re: [O] org to static site?
I've got a single-chord setup with Hugo, adapted from: http://www.holgerschurig.de/en/emacs-blog-from-org-to-hugo/ I'm very pleased with it. - Tory George myglc2 Clemmer writes: On 05/31/2017 at 12:00 Matt Price writes: I'm trying to wean myself off of Wordpress for next year's teaching websites, and am wondering what solutions other people are using for turning a collection of org pages and/or subtrees into a static html site. I am leaning towards Hugo but honestly not for any sensible reason; I've seen other people use Jekyll, though the fact that Github doesn't support direct conversion from org-mode removes some of Jekyll's appeal; and I know there are a number of other solutions too. So, I would love to hear what you all recommend. [...] No doubt too late for your teaching website, but you may find this interesting ... https://github.com/myglc2/emacsite HTH - George
[O] Bug: ps-print-buffer-with-faces does not work properly in column view [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/share/emacs/27.0.50/lisp/org/)]
Hello Org Mode community #+COLUMNS: %ITEM * Test item Some text here test.org.ps Description: PostScript document 1. What exactly did you do? In any orgmode file, like the one attached, I did: 1.1 M-x org-mode 1.2 C-c C-x C-x (org-columns) 1.3 C-u ps-print-buffer-with-faces (output attached) 2. What did you expect to happen? Org entries should be printed 3. What happened instead? Only the first character '*' is printed. I tested this with other org-mode files, and only the first four characters of headlines were printed. Org-mode files are printed correctly when they are *not* in column view. Data generated with `M-x org-submit-bug-report': Emacs : GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 2017-11-06 Package: Org mode version 9.1.2 (release_9.1.2-40-g6ca906 @ /usr/share/emacs/27.0.50/lisp/org/) current state: == (setq org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-after-todo-state-change-hook '(org-clock-out-if-current) org-metadown-hook '(org-babel-pop-to-session-maybe) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-mode-hook '(#[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-show-block-all append local] 5] #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-archive-hook '(org-attach-archive-delete-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-agenda-before-write-hook '(org-agenda-add-entry-text) org-metaup-hook '(org-babel-load-in-session-maybe) org-bibtex-headline-format-function #[257 "\300^A\236A\207" [:title] 3 "\n\n(fn ENTRY)"] org-babel-pre-tangle-hook '(save-buffer) org-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-occur-hook '(org-first-headline-recenter) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-speed-command-hook '(org-speed-command-activate org-babel-speed-command-activate) org-confirm-shell-link-function 'yes-or-no-p org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow org-rmail-open :store org-rmail-store-link) ("mhe" :follow org-mhe-open :store org-mhe-store-link) ("irc" :follow org-irc-visit :store org-irc-store-link) ("info" :follow org-info-open :export org-info-export :store org-info-store-link) ("gnus" :follow org-gnus-open :store org-gnus-store-link) ("docview" :follow org-docview-open :export org-docview-export :store org-docview-store-link) ("bibtex" :follow org-bibtex-open :store org-bibtex-store-link) ("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete org-bbdb-complete-link :store org-bbdb-store-link) ("w3m" :store org-w3m-store-link) ("file+sys") ("file+emacs") ("doi" :follow org--open-doi-link) ("elisp" :follow org--open-elisp-link) ("file" :complete org-file-complete-link) ("ftp" :follow (lambda (path) (browse-url (concat "ftp:" path ("help" :follow org--open-help-link) ("http" :follow (lambda (path) (browse-url (concat "http:" path ("https" :follow (lambda (path) (browse-url (concat "https:" path ("mailto" :follow (lambda (path) (browse-url (concat "mailto:"; path ("news" :follow (lambda (path) (browse-url (concat "news:"; path ("shell" :follow org--open-shell-link)) ) Best regards. -- Francisco Velázquez
[O] Bug: Incorrect visualization of nodes past the second level [9.1.3 (9.1.3-10-gadfbfd-elpa @ ~/.emacs.d/elpa/org-20171127/)]
Starting from the third level, nodes are shown with two asterisks less than expected. Trying to unfold them will actually fold the whole subtree instead. The bug was present even with a clean Emacs configuration and no packages installed. For the moment, I solved downgrading to org-20171023. Thanks! Emacs : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2017-11-02 Package: Org mode version 9.1.3 (9.1.3-10-gadfbfd-elpa @ ~/.emacs.d/elpa/org-20171127/)
[O] Bug: shiftmeta[left|right] on multi line items [9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 When using lists in org like the following: - - Item 1 - Sub-item 1 - Sub-item 1 - - Item 2 - - Item 3 I can shift them left and right using ~org-shiftmetaright~ or ~org-shiftmetaleft~. This also works on the following list: - - Item 1 - This is a very long sub-item that is definitely going to be longer than 80 characters. - Sub-item 2 - - Item 2 - - Item 3 When my cursor is on the second line ( the line that begins with "This is a very..." I can move the sub-item left and right as expected. When my cursor is on the third line ( the line that begins with "than 80..." I get a message saying: "user-error: This command is active in special context like tables, headlines or items" Because this *does* work when my cursor is on the above line, I know org knows how to handle multi line items. Therefore I think it's a bug that org doesn't recognize the cursor being inside a list when it is on the second line of a multi item list. Hopefully I've explained myself clearly, this is my first time submitting an org bug report. Thanks for the continuing effort going in to org. Please CC me in responses as I'm not subscribed to this list. Nathan Emacs : GNU Emacs 27.0.50 (build 7, x86_64-pc-linux-gnu, GTK+ Version 3.22.26) of 2017-11-20 Package: Org mode version 9.1.2 (release_9.1.2-40-g6ca906 @ /usr/local/share/emacs/27.0.50/lisp/org/) current state: == (setq org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-fontify-whole-heading-line t org-after-todo-state-change-hook '(org-clock-out-if-current) org-metadown-hook '(org-babel-pop-to-session-maybe) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-agenda-files '("/home/current_user/.emacs.d/org-gcal-calanders/schedule.org") org-startup-folded nil org-mode-hook '(highlight-sexp-mode (closure (t) nil (org-bullets-mode 1)) #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-show-block-all append local] 5] #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes turn-on-flyspell) org-archive-hook '(org-attach-archive-delete-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-agenda-before-write-hook '(org-agenda-add-entry-text) org-metaup-hook '(org-babel-load-in-session-maybe) org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn ENTRY)"] org-babel-pre-tangle-hook '(save-buffer) org-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-fontify-quote-and-verse-blocks t org-fontify-done-headline t org-occur-hook '(org-first-headline-recenter) org-structure-template-alist '(("e" "#+BEGIN_SRC emacs-lisp \n?\n#+END_SRC") ("s" "#+BEGIN_SRC ?\n\n#+END_SRC") ("e" "#+BEGIN_EXAMPLE\n?\n#+END_EXAMPLE") ("q" "#+BEGIN_QUOTE\n?\n#+END_QUOTE") ("v" "#+BEGIN_VERSE\n?\n#+END_VERSE") ("V" "#+BEGIN_VERBATIM\n?\n#+END_VERBATIM") ("c" "#+BEGIN_CENTER\n?\n#+END_CENTER") ("C" "#+BEGIN_COMMENT\n?\n#+END_COMMENT") ("l" "#+BEGIN_EXPORT latex\n?\n#+END_EXPORT") ("L" "#+LaTeX: ") ("h" "#+BEGIN_EXPORT html\n?\n#+END_EXPORT") ("H" "#+HTML: ") ("a" "#+BEGIN_EXPORT ascii\n?\n#+END_EXPORT") ("A" "#+ASCII: ") ("i" "#+INDEX: ?") ("I" "#+INCLUDE: %file ?")) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-speed-command-hook '(org-speed-command-activate org-babel-speed-command-activate) org-return-follows-link t org-open-non-existing-files t org-confirm-shell-link-function 'yes-or-no-p org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow org-rmail-open :store org-rmail-store-link) ("mhe" :follow org-mhe-open :store org-mhe-store-link) ("irc" :follow org-irc-visit :store org-irc-store-link) ("info" :follow org-info-open :export org-info-export :store org-info-store-link) ("gnus" :follow org-gnus-open :store org-gnus-store-link) ("docview" :follow org-docview-open :export org-docview-export :store org-docview-store-link) ("bibtex" :follow org-bibtex-open :store org-bibtex-store-link) ("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete org-bbdb-complete-link :store org-bbdb-store-link) ("w3m" :store org-w3m-store-link) ("file+sys") ("file+emacs") ("doi" :follow org--open-doi-link) ("elisp" :follow org--open-elisp-link) ("file" :co
[O] org-mode pcomplete does not complete added babel extra languages
For example, I have a package =ob-restclient= installed. I type ~
Re: [O] org to static site?
On 05/31/2017 at 12:00 Matt Price writes: > I'm trying to wean myself off of Wordpress for next year's teaching websites, > and am wondering what solutions other people are using for turning a > collection of org pages and/or subtrees into a static html site. I am leaning > towards Hugo but honestly not for any sensible reason; I've seen other people > use Jekyll, > though the fact that Github doesn't support direct conversion from org-mode > removes some of Jekyll's appeal; and I know there are a number of other > solutions too. > > So, I would love to hear what you all recommend. [...] No doubt too late for your teaching website, but you may find this interesting ... https://github.com/myglc2/emacsite HTH - George
[O] Bug: Dead links from clocking tables to other org files in HTML export [9.1.3 (9.1.3-2-g322612-elpa @ /home/mrhn/.emacs.d/elpa/org-20171120/)]
When exporting my project with org-publish, the exporter generates anchors with names such as "orga79e495" and refers to them when linking to the headers from other files. However, the generated anchor names don't match between files, resulting in all links being dead. Furthermore, the publishing directory is not respected, so all links still point to the directory that the org file was in, even though the html files are located elsewhere. Example: I have put the files needed to reproduce this at https://gist.github.com/martinhansdk/f81a5fdf340eab591e6df55645cfd22d They can be viewed there or fetched with git: git clone https://gist.github.com/martinhansdk/f81a5fdf340eab591e6df55645cfd22d Run emacs -Q -l minimal-org.el Then export with M-x org-publish org I get files in the exported/ subdirectory. The last link in the clocking table in exported/time.html is Worked on supporting ä, ö, and ü But that should have been Worked on supporting ä, ö, and ü Note that both the path is absolute where it should have been relative and the anchor is wrong. As far as I can tell, both problems stem from the fact that the links in the clocking table are absolute file system links. This is, however how the clock table code (org-dblock-update) formats the table. If I manually transform the links in time.org to manual links, then the HTML links are no longer dead. As an aside, is there any way to prevent the following line from appearing in the exported HTML? #+BEGIN: clocktable :scope agenda :link t :maxlevel 5 Thanks, Martin Emacs : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.11) of 2017-09-12 on hullmann, modified by Debian Package: Org mode version 9.1.3 (9.1.3-2-g322612-elpa @ /home/mrhn/.emacs.d/elpa/org-20171120/) current state: == (setq org-tab-first-hook '(org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-speed-command-hook '(org-speed-command-activate org-babel-speed-command-activate) org-link-file-path-type 'relative org-occur-hook '(org-first-headline-recenter) org-metaup-hook '(org-babel-load-in-session-maybe) org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"] org-latex-format-inlinetask-function 'org-latex-format-inlinetask-default-function org-confirm-shell-link-function 'yes-or-no-p org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default org-latex-format-headline-function 'org-latex-format-headline-default-function org-after-todo-state-change-hook '(org-clock-out-if-current) org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn ## CONTENTS)"] org-odt-format-headline-function 'org-odt-format-headline-default-function org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-mode-hook '(#[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-show-block-all append local] 5 "\n\n(fn)"] #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook org-babel-show-result-all append local] 5 "\n\n(fn)"] org-babel-result-hide-spec org-babel-hide-all-hashes) org-bibtex-headline-format-function #[257 "\300\236A\207" [:title] 3 "\n\n(fn ENTRY)"] org-archive-hook '(org-attach-archive-delete-maybe) org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS WIDTH)"] org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-confirm-elisp-link-function 'yes-or-no-p org-metadown-hook '(org-babel-pop-to-session-maybe) org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"] org-html-format-headline-function 'org-html-format-headline-default-function org-link-parameters '(("id" :follow org-id-open) ("rmail" :follow org-rmail-open :store org-rmail-store-link) ("mhe" :follow org-mhe-open :store org-mhe-store-link) ("irc" :follow org-irc-visit :store org-irc-store-link) ("info" :follow org-info-open :export org-info-export :store org-info-store-link) ("gnus" :follow org-gnus-open :store org-gnus-store-link) ("docview" :follow org-docview-open :export org-docview-export :store org-docview-store-link) ("bibtex" :follow org-bibtex-open :store org-bibtex-store-link) ("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete org-bbdb-complete-link :store org-bbdb-store-link) ("w3m" :store org-w3m-store-link) ("file+sys") ("file+emacs") ("doi" :follow org--open-doi-link) ("elisp" :follow org--open-elisp-link) ("
[O] Best way to check if a subtree with a property exists?
Hello, I'd like to check if the current Org file has at least one subtree with a specific property (EXPORT_FILE_NAME in my case). What's the most efficient way to do that? Below works.. but I can see that it's not efficient.. it maps through the whole Org file: (let ((total-valid-subtrees (let ((valid-subtrees (org-map-entries (lambda () t) ;Return value does not matter here ;; Only map through subtrees where ;; EXPORT_FILE_NAME property is not ;; empty. "EXPORT_FILE_NAME<>\"\""))) (safe-length valid-subtrees (if (= 0 total-valid-subtrees) (message "invalid") (message "valid"))) So, - How can I quit out of org-map-entries as soon as the first matching entry is found? - What's a better way to do the same? Thanks. -- Kaushal Modi
[O] schedule third last day of every month
Hi, Can it be possible to schedule third last day of every month? Thanks, Matt
Re: [O] Best way to check if a subtree with a property exists?
On Fri, Dec 1, 2017 at 9:00 AM Kaushal Modi wrote: > - How can I quit out of org-map-entries as soon as the first matching > entry is found? > I think this is much better: (let ((valid-found (catch 'break (org-map-entries (lambda () (throw 'break t)) ;; Only map through subtrees where ;; EXPORT_FILE_NAME property is not ;; empty. "EXPORT_FILE_NAME<>\"\"" (message "valid-found: %S" valid-found)) - What's a better way to do the same? > Comments are welcome :) Thanks. -- Kaushal Modi
[O] RFC better Unicode support - Unicode Characters causing problems with TAGs etc.
Hi, I have been experimenting with some Unicode symbols as part of my TODO and TAG definitions, to mixed results. I would like to propose that they are given first class support, especially in tags and priorities. Also, are other people using Unicode, and if so, how? especially with visually consistent tables, does anyone have a a good mono-spaced to recommend? Here is some stuff to play with: #+PRIORITIES: ❢ ☯ ⧖ #+TAGS: emacs⚙ ⌚yakshaving #+SEQ_TODO: ☐TODO ❢☐ ☯☐ ⌚☐ ⚙☐ ✍☐ ⧖ | ✔☺ ✔ ✘ ☑ ☒ ☓ ☑DONE ☒CANCELLED ☓ TODO fastkeys and similar seem to work Tables: | symbols| Interpretation | | | | | ❢☐ || | | | | ❢TODO || | | | | ⌚☐WAITING || | | | | ⧖WAITING || | | | | ✔☺ || | | | | ✔DONE || | | | | ✘ || | | | | ☑ || | | | | ☒ || | | | | ☓ || | | | * [#⧖] ❢☐ add ispell write mode hook to saving journals :emacs⚙: --- Tim.
Re: [O] exporting "flattened" tagged subtrees
Michel Damiens writes: > Hello, > > I would like to export and org file in such a way that : > - only tagged subtrees are exported (for a specific tag) > - the tree structure is "flattened" > > for example a file example.org containing : > * heading 1 :tag: > ** subheading 1.1 > content 1.1 > ** subheading 1.2 :tag: > content 1.2 > *heading 2 > ** subheading 2.1 :tag: > content 2.1 > ** subheading 2.1.1 :tag: > ** subheading 2.1.2 :tag: > content 2.1.2 > ** subheading 2.2 > content 2.2 > > would be exported to the file example.org.org containing : > * heading 1 > * subheading 1.2 > content 1.2 > * subheading 2.1 > content 2.1 > * subheading 2.1.1 > * subheading 2.1.2 > content 2.1.2 > > (which in turn would be exported to latex, beamer or html for example) The first part you can archive with these tags: #+SELECT_TAGS:, #+EXCLUDE_TAGS: These lines provide settings for exporting files. For more details see Export settings . Flatting the file can be done by search and replace (while (search-forward-regexp "^*+ " nil t) (replace-match "* ")) Rasmus -- ツ