Re: [BUG] error after reading in contents of other file [9.6 (9.6-??-e7ea951 @ /home/user/.emacs.d/.local/straight/build-28.0.50/org/)]

On Sat, Mar 12, 2022 at 7:53 AM Ihor Radchenko wrote: > > Thanks for the report! > Are you still seeing the traceback if you update Org to latest main? > 5da9d6810 in more recent versions should help with some cases when the > error like in your backtrace appears. Yes, I'm still getting the follo

[BUG] error after reading in contents of other file [9.6 (9.6-??-e7ea951 @ /home/user/.emacs.d/.local/straight/build-28.0.50/org/)]

I manually opened a new daily file, and read in some content from another file (using ':r filename.txt' with Evil). After doing this, the content was inserted, but the following traceback occurred: Warning (org-element-cache): org-element--cache: Org parser error in 2022-03-10.org::193. Resett

Re: [O] Smart archiving of subtrees with parent headlines

off wrote: > > On Tue, May 1, 2018 at 11:01 AM Bastien wrote: > >> Hi Mark, >> >> Mark Edgington writes: >> >> > I don't know why not -- I'm OK with the code being used in >> > org-archive.el. As far as I'm concerned, you c

Re: [O] Smart archiving of subtrees with parent headlines

Hi Bastien, On Thu, Apr 26, 2018 at 7:34 PM, Bastien wrote: > I'd be interested in integrating such a functionality in > org-archive.el. > > Do you think that is feasible? I don't know why not -- I'm OK with the code being used in org-archive.el. As far as I'm concerned, you can use it however

Re: [O] FILETAGS tags hidden by TAGS option

Hi Nicolas, >> >> For example, with the following options, the foo tag will not show up >> when trying to do tab-completion, but only bar and baz will: >> >> #+TAGS: bar baz >> #+FILETAGS: foo > > FWIW, I cannot reproduce it (from master, I didn't check maint). You may > want to update Org and t

[O] FILETAGS tags hidden by TAGS option

When using org-tags-view, the list of tags used for tab-completion fails to include tags specified via the #+FILETAGS option when there exists a #+TAGS option in the file which doesn't contain the #+FILETAGS tags. For example, with the following options, the foo tag will not show up when trying to

Re: [O] Smart archiving of subtrees with parent headlines

While further evaluating my code, I realized that it wasn't working when target headlines contained tags. I've updated the code to handle this case -- the result is posted as a gist since it may change later on, and all of you esteemed elisp hackers can more easily contribute to it that way, until

Re: [O] Smart archiving of subtrees with parent headlines

On Mon, Feb 12, 2018 at 1:54 AM, Ken Mankoff wrote: > > Does the attached file here work for you? I use it and it seems to do what > you describe. > > https://lists.gnu.org/archive/html/emacs-orgmode/2014-08/msg00109.html > Ken, I tried the code you included from your config file, and while it d

[O] CI for worg

Is there any kind of build-server connected with publishing org-mode documentation and/or the worg website? I ask because I have seen problems like the dead link here: https://orgmode.org/worg/org-contrib/babel/languages.html (which is referred to in https://orgmode.org/worg/org-contrib/babe

[O] Smart archiving of subtrees with parent headlines

Hello all, I have looked at a few threads related to the archiving of subtrees, but haven't found anything that matches what I think would be a very sensible archiving behavior. I already posted this as a question on the emacs stack-exchange site (https://emacs.stackexchange.com/questions/38530/h

Re: [O] Blank lines in LaTeX output due to org-mode comments

On Thu, Jun 30, 2016 at 5:23 PM, Nicolas Goaziou wrote: > Mark Edgington writes: > >> I'm inclined to view it more as a bug, because it makes it impossible to >> place comments within a paragraph. > > This is per Org syntax. "# ..." is not meant as an inl

Re: [O] Need to update documentation to reflect export block syntax

Kaushal Modi gmail.com> writes: > Mark The online documentation corresponds to the stable releases of org-mode only. > The master branch is the dev branch. The only way to access the latest documentation is via the Info manual (M-x info in emacs to access that is the best way IMO). Thanks, I s

Re: [O] Blank lines in LaTeX output due to org-mode comments

One other use case: when you want to comment out a single line in a paragraph, or have a few different lines within a paragraph that you wish to be able to select among by leaving only only one of them uncommented.

Re: [O] Blank lines in LaTeX output due to org-mode comments

Nicolas Goaziou nicolasgoaziou.fr> writes: > Mark Edgington gmail.com> writes: > > > Assume we have the following sample org-mode document: > > > > * Test Heading > > test test test test test test test > > test test test test test test test > > te

[O] Blank lines in LaTeX output due to org-mode comments

Assume we have the following sample org-mode document: * Test Heading test test test test test test test test test test test test test test test test test test test test test # HERE IS A COMMENT TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TES

Re: [O] Need to update documentation to reflect export block syntax

It also might be worthwhile to have org-mode warn users (at least for a number of new releases) who happen to be using the old format, explaining that they need to use the new one to avoid problems when exporting.

[O] Need to update documentation to reflect export block syntax

I recently updated my org-mode git repository (for a long time I've had an older git version that I was using), and I am now having problems when doing latex exports. I bisected with git to find that the "problem" starts with this revision: commit 54318add34f09ff39d3fd034a4c1a89f60fd8759 Author:

Re: [O] org-export-with-broken-links doesn't apply to footnotes

Nicolas Goaziou nicolasgoaziou.fr> writes: > No, it isn't. However I could only reproduce it with empty footnote > definitions. > > In any case, this is now fixed. Thank you. I am providing a minimal example that still exhibits the problem for me (on the latest git rev): --- BEGIN EXAM

[O] org-export-with-broken-links doesn't apply to footnotes

The org-export-with-broken-links option was introduced in order to allow exports to proceed when a link isn't able to be resolved. Sometimes this happens when trying to export a narrowed region of a buffer. I have noticed, however, that even if I have (setq org-export-with-broken-links 't), I am s

Re: [O] Restoring the org-freemind-to-org-mode function

On Dec 21, 2015 5:14 AM, "Vaidheeswaran C" < vaidheeswaran.chinnar...@gmail.com> wrote: > > Note: I would like to ensure that the file moves out of it's current > obscure place in contrib/lisp of Orgmode to a more visible place like > GNU ELPA before I expend any efforts on improving it. Why is EL

Re: [O] Restoring the org-freemind-to-org-mode function

On Dec 17, 2015 8:36 AM, "Nicolas Goaziou" wrote: > > org-freeming.el was replaced with ox-freeming.el, in contrib directory. > You may want to contact its author (which may not read this list) and > discuss if it would be possible to include the feature in that library > instead. > Hi Nicolas,

[O] Restoring the org-freemind-to-org-mode function

I have in the past used the org-freemind-to-org-mode function, which is no longer included in org-mode. It used to be part of org-freemind.el file (see http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob_plain;f=lisp/org-freemind.el;hb=8f49547aaf0f9396f2a0bcfb25ce2c33be5e91fd ). I have since

[O] Comment lines interfere with figure options

If I have some org-mode content that looks like this... #+NAME: fig-myimage #+CAPTION: Caption of Figure #+ATTR_LaTeX: :width 5cm #+RESULTS: myimage [[file:images/myimage.png]] then I get a centered figure with the appropriate width and caption when exporting to LaTeX. If, however, I add a comme

Re: [O] org-collector unable to handle macros

Aaron Ecay gmail.com> writes: > > This looks like the same problem I reported (and provided a patch for) here: > . Some orgtbl-* > functions can’t cope with macro (or macro-resembling) text, because they > use the exporter, which expects a

Re: [O] org-collector unable to handle macros

Nicolas Goaziou nicolasgoaziou.fr> writes: > > Mark Edgington gmail.com> writes: > > > On Aug 31, 2015 6:43 PM, "Nicolas Goaziou" nicolasgoaziou.fr> wrote: > >> > >> Hello, > >> > >> Mark Edgington gmail.com> writes: &

Re: [O] org-collector unable to handle macros

> >> > >> :INCLASS: ABC {{{c(stuff)}}} DEF > >> > >> looks incorrect. Macros are not expanded in node properties (with an > >> exception for :EXPORT_SOMETHING: when #+SOMETHING is parsed). > > > > It is not intended to be expanded when generating the table, but the table > > should have the macr

Re: [O] org-collector unable to handle macros

On Aug 31, 2015 6:43 PM, "Nicolas Goaziou" wrote: > > Hello, > > Mark Edgington writes: > > > Charles Millar verizon.net> writes: > > > >> This may be related to the problem or is the same that I reported in > >> April and May and agai

Re: [O] org-collector unable to handle macros

Charles Millar verizon.net> writes: > This may be related to the problem or is the same that I reported in > April and May and again earlier this month when Bastien's requested > details in his August 4th message. Have you (or anyone else) been able to reproduce the problem given the example w

[O] org-collector unable to handle macros

I have had problems getting org-collector.el to generate tables where the content of the tables should include macros. At some point in the past this worked, but at this time (latest git version of org-mode), the following example fails (unless you remove the macro from the property definition):

[O] bad interaction between yasnippet and org-mode

I have a yas snippet that looks like the following: * $1 :sometag: $0 When I try to expand this snippet (on an empty line) in an org-mode buffer, there seems to be a bad interaction happening between org-mode and yasnippet, such that when entering in text at the $1 location, ty

[O] Bug: todo states not logged to drawer when using narrowed indirect buffer [8.3beta (release_8.3beta-1203-g93cc5f) ]

To reproduce this bug, do the following: 1. edit / open the following org file: #+TODO: TODO(t) WAIT(w!) | DONE(d!) CANCELED(c!) #+STARTUP: logdrawer * testing A some stuff * testing B 2. execute (org-tree-to-indirect-buffer) on the 'testing A' headline 3. go to the end o

Re: [O] LaTeX_HEADER blocks

I noticed there was also a newer thread (around a year old) on this topic. It seems that what Nicolas Goaziou proposed earlier (about using #+attr_latex to modify whether a latex block is a header block or not) has not yet been implemented. This would be an alternative, though I find it more cryp

[O] LaTeX_HEADER blocks

Hi Everyone, It is possible in org-mode to do either #+LaTeX: \somecommand or #+BEGIN_LaTeX \somecommand #+END_LaTeX I typically use the latter (the block form) because I often have multiple lines of LaTeX I would like to include at certain locations of a document. Similar to

Re: [O] math in footnotes not exported correctly when a buffer is narrowed

Rasmus gmx.us> writes: > > It was fixed a while ago in master. Are you using 8.2? Oh, I thought I was using something more recent, since the version was named "8.3beta", but apparently that's old. Thanks! A slight digression: I noticed, when cloning the git repo, that the current repo size

[O] math in footnotes not exported correctly when a buffer is narrowed

I've noticed a bug in org-mode's LaTeX exporting of footnotes when a buffer is narrowed to a particular section. To reproduce, try to export the following org-file to a LaTeX document, and inspect the resulting LaTeX code -- it will have stripped the math environment off of "\tau_s": * Test Sect

[O] Babel blocks get unindented when making changes outside the blocks

Hello all, Given the following code: - BEGIN CODE - * some headline - blah - blah - blah - blah - blah #+begin_src octave first line if (num <= 2) stuff end #+end_src - blah # some comments # more comments 1. item 1

[O] fontification of comment blocks (or any other kind of block)

It seems that there is nothing in place to allow the text inside blocks like: #+BEGIN_COMMENT ... #+END_COMMENT from having its face customized. It is possible to do this with quote and verse blocks, only not comment blocks. Would it be sensible to have a "default" block face which applies to *

Re: [O] proposal to have ignoreheading tags/properties

s. >> >> Eric's filter, like any other filter, has flaws that cannot be fixed. >> Useful filters ought to be published in Worg, not included in core. > > Fair enough. > > Still, can someone add Eric's solution to contrib/lisp/ox-extra.el? > > Thank

Re: [O] proposal to have ignoreheading tags/properties

Hi Rasmus, Rasmus gmx.us> writes: > > Bastien gnu.org> writes: > > > > I think Eric's filter is important enough to be in core, together > > with an option to let users decide what tag should be used instead > > of "ignore" (with "ignore" as a default). > > How about "ignoreheading" as this i

Re: [O] proposal to have ignoreheading tags/properties

Hi Bastien, On Sun, Jul 27, 2014 at 1:21 PM, Bastien wrote: > > I suggest renaming ox-extra.el to ox-filters-extra.el and to have > org-mode/lisp/ox-filters.el for filters that are important enough > to be in core. > Your suggestion sounds sensible, but of course I'm biased, as I've been using

Re: [O] proposal to have ignoreheading tags/properties

Nicolas Goaziou nicolasgoaziou.fr> writes: > Moreover, that task is highly specific; I'm not convinced we should have > a dedicated keyword for each of them. I'd rather have a simple solution > for selective export problems, even if, as a generic solution, it may > look clumsier. Hi Nicolas, I

Re: [O] proposal to have ignoreheading tags/properties

Nicolas Goaziou nicolasgoaziou.fr> writes: > Actually, the problem is deeper than that. This :inline: tag is just > a convoluted way to ask for a positive answer to another FAQ: « Can > I close an outline section without starting a new section? » > (http://orgmode.org/worg/org-faq.html#closing-ou

Re: [O] proposal to have ignoreheading tags/properties

Eric Abrahamsen ericabrahamsen.net> writes: > > It looks like a groundswell for remove-andor-promote tags for headlines, > but for the sake of argument let me propose the use of blocks. It seems > to me that something like a "generic block" (a block that does nothing > but delete its begin/end de

Re: [O] proposal to have ignoreheading tags/properties

Eric Schulte gmail.com> writes: > Ken Mankoff gmail.com> writes: > > > > I don't think the word "inline" signifies that a heading will or won't > > be exported and/or its children promoted. > > > > Can you suggest a more intuitive/appropriate tag name? Would it be possible / sensible to allow

Re: [O] proposal to have ignoreheading tags/properties

Thorsten Jolitz gmail.com> writes: > > In a tree structure, when ignoring the parent node, it seems only > logical that the siblings are ignored too. > > You seem to use the wrong tool for the task (headlines), this looks like > a perfect use case for TAGS, i.e. define your (concept) groups as

[O] proposal to have ignoreheading tags/properties

In using org-mode, there is one problem that has always irked me (and is apparently also closely related to the FAQ "How do I ignore a headline?"). When I am writing something, I sometimes want to group things by concept or by work to be done, or any other number of groupings. BUT I do not want t

Re: [O] bug in org-element-footnote-definition-parser?

Nick Dokos gmail.com> writes: > > Nicolas Goaziou gmail.com> writes: > > > Hello, > > > > Mark Edgington gmail.com> writes: > > > >> I have encountered the following error message when trying to export > >> to latex the attached

[O] bug in org-element-footnote-definition-parser?

I have encountered the following error message when trying to export to latex the attached example org file: org-element-footnote-definition-parser: Invalid search bound (wrong side of point) What is curious is that changing the number of ""'s in [fn:1] to 2 instead of 3 allows it to compile.

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

Nicolas Goaziou gmail.com> writes: > > You can remove offending packages with `org-export-before-parsing-hook' > if you don't want them to be used during the export process. > Yes, but I need the package which is buggy. If I were to remove it, I couldn't preview latex fragements or export a PD

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

Ok, I dug into the problem a little deeper, and it seems that it really can be considered a bug in the circuitikz code -- in order to remedy it for the present time, the circuitikz.code.tex file from this package should be modified, and the line: \ctikzset{color/.initial=black} must be removed /

Re: [O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

On Wed, Dec 11, 2013 at 3:46 AM, Eric S Fraga wrote: > Mark Edgington writes: > > [...] > >> Is there any way that I can make it so that without a lot of "hacks" I >> can make the previews appear as white-on-black, and the PDFs print >> black on white?

[O] TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together

Hello everyone, Assume I have an org-mode file that contains the following: -- #+OPTIONS: tex:imagemagick #+LaTeX_HEADER: \usepackage[siunitx]{circuitikz} * Test circuit #+begin_lateX \begin{circuitikz}[scale = 1.0] \draw (0,0) node[anchor=east]{$V_{in} -$}

[O] [PATCH] org-collector: enable specifying a default table-value as a parameter

Hi Bastien, Sorry about the formatting -- that's annoying. I've attached the patch. Here's its description: Currently there isn't an easy way to have default cell values which differ from one propview block to another. This patch enables one to specify what a cell's default value for a bl

[O] [PATCH] org-collector: enable specifying a default table-value as a parameter

Currently there isn't an easy way to have default cell values which differ from one propview block to another. This patch enables one to specify what a cell's default value for a block should be. For example, with this patch applied, you can do something like: #+BEGIN: propview :id " myt

Re: [O] Difference between LaTeX and HTML exported documents for bold verbatim text

Aaron Ecay gmail.com> writes: > > It would be nice if both exporters were consistent in how they export > > the styles for these cases (it seems like the HTML exporter gets it > > right, while the LaTeX exporter doesn't). > > This is an issue of the default font in LaTeX not providing the right

[O] Difference between LaTeX and HTML exported documents for bold verbatim text

Hello all, I have noticed that it if you have text like the following in org-mode: A *B* *=C=* then exporting to HTML causes A to be normal, B to be bold, and C to be bold and fixed-width font. Exporting the same to LaTeX, however, causes A to be normal, B to be bold, and C to be only fixed-wid

Re: [O] Arbitrary lisp functions in column-attributes

Hi Bastien, On Tue, Nov 5, 2013 at 4:06 PM, Bastien wrote: > One possible negative effect I can see is that users have to be extra > careful what type of output such functions will produce, so that this > output can be used by a summary type. Wouldn't the output of a function be something mutua

Re: [O] Arbitrary lisp functions in column-attributes

Bastien gnu.org> writes: > > FWIW, I'd be inclined to say this is a bit *too much* -- but I'm > curious to see if others have the same need. > Hi Bastien, What about it seems too much? Or put differently, what do you think would be the negative effects of having something like this possible?

Re: [O] Arbitrary lisp functions in column-attributes

> How about using an elisp babel block, with tabular results? Something > like (tested only very lightly): > > #+BEGIN_SRC elisp :results table > (cons >(list "Header A" "Header B") >(cons 'hline > (org-map-entries > (lambda () > (list > (princ

Re: [O] Org-Mode newbie, configuration?

Hi Joe, While it isn't org-mode specific, you might want to take a look at Eric Schulte's "Emacs Starter Kit" configuration (http://eschulte.github.io/emacs24-starter-kit/) -- it includes some org-mode settings, and is an example of a great way of maintaining your emacs configuration. Regards, M

Re: [O] Arbitrary lisp functions in column-attributes

Hi Aaron, I hadn't actually foreseen using it for column-view so much, but rather for a dynamic-block which generates a column-view of a tree. These are, as far as I understand, read-only. I don't think it would work well with read-write column-views, so if such a function were defined in the :CO

Re: [O] Arbitrary lisp functions in column-attributes

Hello all, Since the formatting on my earlier post was bad, I'm re-posting this with a bit more information: I would really appreciate it if it were possible to specify an arbitrary lisp function to process node-properties when creating a column view. Currently it is possible to have something l

[O] Arbitrary lisp functions in column-attributes

Hello all, I would really appreciate it if it were possible to specify an arbitrary lisp function to process node-properties when creating a column view. For example, you can currently have something like: * Top node for columns view :PROPERTIES: :COLUMNS: %25ITEM %TAGS %PRIORITY %TODO

Re: [O] org-babel generated images and +ATTR_LATEX

Hi Mike, That does help -- when testing it, I found that the problem had more to do with my header options than to do with the presence or absence of a #+NAME line. But still, with the header options I gave in my original example, org-babel's behavior does seem strange (maybe buggy?) to me. My w

[O] org-babel generated images and +ATTR_LATEX

Hello all, I have noticed that it seems not possible to evaluate a babel block of code which generates an image, and to have a #+ATTR_LATEX line exist which immediately precedes the generated link to the image. In other words, If there's already a #+ATTR_LATEX line, I need to move it after the bl

[O] Orgmode fails to export specific web-links as latex/pdf

Hello all- When trying to export via latex -> pdf, the following org-mode snippet fails to compile. Presumably there's something that should be changed in the export filters? Here's the org-mode snippet: - *** [[http://www.example.com:90/search~S2?/Xsearchterm&searchscope%3D

[O] Unable to use "+LaTeX_HEADER: \input{...}" with latex-preview-fragment

I attempted recently to have org-mode use a preamble file when previewing latex-fragments. I used a line like the following: +LaTeX_HEADER: \input{relative-path-to-file.tex} Unfortunately, the file referenced by the \input{} command doesn't get copied to the location where the preview tex fi

Re: [O] [PATCH] Export: Override headline numbering via properties

Hi Nicolas, On Mon, May 13, 2013 at 6:54 AM, Nicolas Goaziou wrote: > > You can still number these parts manually with, e.g., > > #+latex: \section*{Introduction} > > before the first section in your Org document. > While this is possible, wouldn't this break the structure of the org-document,

Re: [O] [PATCH] Export: Override headline numbering via properties

Also, I forgot to mention that the patch is tested, and behaves as expected. On Mon, May 13, 2013 at 2:18 AM, Nicolas Goaziou wrote: > Thanks for your patch. > > Though, I don't get what you are trying to achieve nor what a use case > would be. Have you tested this patch ? It may not behave as yo

Re: [O] [PATCH] Export: Override headline numbering via properties

Hi Samuel, I'd guess it isn't exactly the same as what you did -- I assume you are making it possible to modify the numbering level threshold via properties. Is this modification inherited by child-headlines or not? Either way, there would be a lot of "hackery" required to use this to achieve th

Re: [O] [PATCH] Export: Override headline numbering via properties

Hello Nicolas, I'm sorry for not having provided more explanation of the patch's purpose. The motivation is basically to permit any kind of "manual" (in contrast to "automatic") control over the section-numbering behavior connected with a particular headline. In LaTeX, for example, you are able

[O] [PATCH] Export: Override headline numbering via properties

* lisp/ox.el (org-export-numbered-headline-p): If the `:NUMBERED' property is defined for a headline, turn numbering on when the property value is "y" (otherwise turn numbering off). Do the same if the `:INHERITED_NUMBERED' property is defined for a headline, except make this property inherited by

[O] keymap for read-date-minibuffer

Hello all, I recently spent a while figuring out how to add custom-keybindings to the read-date-minibuffer which appears when org-read-date is called. The only way to do it currently is to use the org-read-date-minibuffer-setup hook, and add keybindings to the minibuffer-local-map there. I'm wond

[O] Announcing a script that connects org-mode and google-tasks

Hello all- I hacked together a python script based on some already-existing code, which allows one to push an org file to a google-tasks list, or to pull the contents of a google-tasks list into an org file. Though the code isn't beautiful at the moment, it is functional. Feel free to improve it