[tip] Insert arbitrary LaTeX code at the beginning of any float environment

Hi all, If we want to introduce arbitrary LaTeX code at the very beginning of a float environment, apart from the usual tricks of putting the code in :caption or :placement, this solution I describe here is more from the LaTeX side. I thik its advantages are more control and consistency from the

Re: [PATCH] org-attach: Attach current Gnus article parts

Ihor Radchenko writes: > I think that a good example implementation is from notmuch.el. It does > not use anything specific to notmuch, just built-in mm-*.el from gnus: Thanks for the tip, Ihor. I'll take a look at it, and see if I can sketch something usable... Best regards, Juan Manuel

org-agenda-clock-report-header

Hello, Could more information perhaps be added to the doc string of "org-agenda-clock-report-header"? And an example would be very useful. As it stands at present, I haven't a clue as to what the variable does and why it might be useful. Thank you. Colin Baxter.

how to best correct exams (code matlab) using org mode (and tables)

Hi I came around https://kitchingroup.cheme.cmu.edu/blog/2013/10/23/Writing-exams-in-org-mode/ Which is a bit outdated. My use case are to correct of matlab files, so usually I have a single org file with a table and insert the results. However what I missing is that my comments, and

Re: Export LaTeX command inside figure environment

On 08/05/2022 13:06, Thomas S. Dye wrote: It would be better to have a LaTeX attribute, say :commands, that places commands within \begin{figure} ... \end{figure}. Look at the code of `org-latex--inline-image' and variants of markup it may generate. There are too may places where :commands

Re: Bug: Percentage in caption (even escaped) does not work in LaTeX export

Hi All, This should be finally fixed in when it’s merged. All the best, Timothy

Re: Export LaTeX command inside figure environment

Thomas S. Dye writes: > It would be better to have a LaTeX attribute, say :commands, that > places commands within \begin{figure} ... \end{figure}. This is a possible solution from the LaTeX side, which would avoid having to modify the Org code and can also be used to introduce more complex

Re: [PATCH] (v2) New LaTeX code export option: engraved

Hi Daniel & co., I have a new set of patches (attached), which make use of a major new feature in engrave-faces v0.3: engraved themes. Now, the theme used for source blocks can be set by the document keyword `#+latex_engraved_theme: THEME-NAME'. Furthermore, the theme can be customised on a

Re: Concatenate properties

Tyler Grinn writes: > > Could you provide an example of what the value of that variable would be > if, for instance, I wanted PROP_A and PROP_B to be joined with a single > space and PROP_C and PROP_D to be concatenated? Or better yet, have the > default be to join with a single space for any

Re: Recent changes in org-fold regarding emphasize visibility

Ihor Radchenko writes: > I have made changes in invisible edit handling. > Now, when using 'text-properties style, > org-fold-check-before-invisible-edits ignores folded links just like it > does with overlays style. > > The commit is 2e4ed52b1. Looks good; thank you Ihor! -- Daniel

Re: [PATCH] org-attach: Attach current Gnus article parts

Juan Manuel Macías writes: > What I don't quite understand is why it wouldn't be appropriate to add a > new entry with the new feature to the org-attach menu. Thinking about it more, new feature in org-attach menu should actually be ok. My initial logic was that we cannot easily select attach

Re: Concatenate properties

Ihor Radchenko writes: > Tyler Grinn writes: > >> John Kitchin writes: >> >>> I like the variable idea. I would make it a concatenation string for >>> joining. That way “” would concatenate the way Tyler wants, “ “ would >>> preserve current behavior, and “,” could lead to a comma separated

Re: Problem with org-babel and geiser

Rudolf Adamkovič writes: > P.S. > > We should add 'testing/lisp/test-ob-scheme.el' or it will break again > sooner or later. Can we make the Org test suite depend on Geiser and > Guile? Given that Org uses Geiser out of the box, I think we should. > What do you think? Sounds reasonable.

Re: org-agenda-filter-by-tag doco

Fair enough. I follow your reasoning and it seems sound. Please close. On Sun, 8 May 2022 at 14:07, Ihor Radchenko wrote: > > Phil Hudson writes: > > > I'd like to expand the docstring of command `org-agenda-filter-by-tag` > > to document the Elisp equivalent of interactive prefix arguments. By

Re: [PATCH] org-attach: Attach current Gnus article parts

Ihor Radchenko writes: > I think that supporting only Gnus is too specific. Not all the people > use Gnus as mail reader. And the extra menu option you propose will only > eat up space for people not using Gnus. > > I'd prefer a more generic approach working in any kind of email reader, > be it

Re: org-agenda-filter-by-tag doco

Phil Hudson writes: > I'd like to expand the docstring of command `org-agenda-filter-by-tag` > to document the Elisp equivalent of interactive prefix arguments. By > trial and error and guesswork I determined that I could emulate `C-u > C-u` by passing `'(16)` as the second argument >

Re: [PATCH] org-attach: Attach current Gnus article parts

Juan Manuel Macías writes: > In the attached patch I add a new command for org-attach: save *all* > attachments from the current Gnus article to the current org-attach-dir. > > (Sorry for repeating the word "attach" so much :-)) > > NB: > > 1. If no Gnus article is open, it returns an error

Re: Concatenate properties

Tyler Grinn writes: > John Kitchin writes: > >> I like the variable idea. I would make it a concatenation string for >> joining. That way “” would concatenate the way Tyler wants, “ “ would >> preserve current behavior, and “,” could lead to a comma separated >> list for example. Other things

Re: [BUG] org-complex-heading-regexp should consider COMMENT keywords [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)]

Ignacio Casso writes: >> I have added TINYCHANGE cookie as you don't appear to have FSF copyright > > I should have it, I did the paperwork for commit 2b564f504b in > Emacs. Maybe I used a different email? Or maybe the problem is that now > that I see it I don't have my full name configured in

Re: [BUG] org-complex-heading-regexp should consider COMMENT keywords [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)]

> Thanks! Thank you too! > I have added TINYCHANGE cookie as you don't appear to have FSF copyright I should have it, I did the paperwork for commit 2b564f504b in Emacs. Maybe I used a different email? Or maybe the problem is that now that I see it I don't have my full name configured in git.

Re: [BUG] org-complex-heading-regexp should consider COMMENT keywords [9.5.2 (release_9.5.2-25-gaf6f12 @ /home/ignacio/repos/emacs/lisp/org/)]

Ignacio Casso writes: > Done. I attach the patch: Thanks! Applied onto main as a3dd2 with minor amendments. I have added TINYCHANGE cookie as you don't appear to have FSF copyright assignment and capitalised "match" in the commit summary. Best, Ihor > From

Re: [PATCH] update ob-scheme to latest changes in geiser package

Tim Van den Langenbergh writes: > I have updated the patch and enclosed it, feel free to drop a line if you > notice anything else obviously missing. Thanks! Applied onto main as 06d08e6f3. Best, Ihor

Re: Recent changes in org-fold regarding emphasize visibility

Daniel Fleischer writes: >> The question is what should be the logical behaviour of Org when editing >> text inside or at the border of these hidden text types? How should we >> interpret the values of org-catch-invisible-edits (nil error show >> show-and-error smart)? > > Not sure we need to

Re: org-fold problems

Eric S Fraga writes: > On a related matter, I typically use vc-ediff for comparing the current > working copy of a file and the last committed version. This used to > expand the file completely (assuming I'm remembering correctly) but now > (some?) drawers are not opened so if there are

Re: org-fold documentation

Max Nikulin writes: > Will it help to create files like org-fwd.el with function declarations > to allow other packages (even from org-mode) to use "(require > 'org-fwd.el)" instead of adding a lot of `declare-function' forms that > must be kept in sync with function definitions? It is an

Re: [org-contrib] Take over maintaining of org-contacts.el

"Christopher M. Miles" writes: > Yes, please update to new place: https://repo.or.cz/org-contacts.git. > Thanks for checking this up, I have not realized missed migration of > org-contacts repo. Done in 15b03d5. Best, Ihor

Re: [PATCH] style/worg.css: Display TOC on top

Ihor Radchenko writes: > > The attached patch fixes the issue. Applied as 8d7d0c77

Re: [PATCH] Add unmaintained warnings for applicable blogging tools

thecashewtrader writes: > --- > org-blog-wiki.org | 11 ++- > 1 file changed, 6 insertions(+), 5 deletions(-) Thanks! Applied as ab6ab6d9. Best, Ihor

Re: [PATCH] ob-plantuml: Allow setting PlantUML args for jar file

Max Nikulin writes: > To wrap up, I suggest (and I do not insist) to drop > "-Djava.awt.headless=true" since "-headless" is anyway added in jar > mode. Those who desperately need namely "-Djava.awt.headless=true" (for > some unknown to me reason) may customize :java header argument. I do not

Re: How to export to markdown programmatically without the table of contents?

On 2022-05-07, at 10:16, Max Nikulin wrote: > On 02/05/2022 23:52, Marcin Borkowski wrote: >> On 2022-05-01, at 22:01, Berry, Charles wrote: On May 1, 2022, at 2:20 AM, Marcin Borkowski wrote: I'd like to export a Org-mode formatted string to markdown, but without the table

Re: #4 Org mode profiling meetup on Sat, May 7

Ihor Radchenko writes: > Ihor Radchenko writes: > >> The time will be the same: 9pm SG time (4pm Kyiv; 2pm London; 9am New >> York). Sat, May 7 >> >> I will post the link to the meeting one hour before the meeting start. > > Meeting link: https://teamjoin.de/Org-dev-profiling-20220507-d708k

Re: Export LaTeX command inside figure environment

Aloha Max, Max Nikulin writes: On 08/05/2022 07:30, Juan Manuel Macías wrote: Thomas S. Dye writes: Is there a way to add an arbitrary LaTeX command between \begin{figure} ... \end{figure} during LaTeX export? I want to end up with the following snippet, but can't figure out how to slip