Re: [O] computing the size of a tikz to png image during export

On Wednesday, 24 Jan 2018 at 08:54, Alan Schmitt wrote: > If I understand how it works in the png case, a standalone latex file is > first generated, then it is compiled to pdf and converted to png using > imagemagick. Instead of specifying the geometry of the image (width of > 800 pixels above),

Re: [O] properties using other properties

I recommend looking into org-edna (http://www.nongnu.org/org-edna-el/#conditional_forms). You can try to use "has-property" in combination with "set-property" as a TRIGGER. Alternatively, you can customize org-property-changed-functions (see

[O] computing the size of a tikz to png image during export

Hello, I use this great trick to have both a pdf and html export of tikz images: #+header: :file (by-backend (latex "tp6-tree.tikz") (t "tp6-tree.png")) #+header: :imagemagick yes :iminoptions -density 600 :imoutoptions -geometry 800 #+header: :results file raw #+header: :fit yes #+header:

Re: [O] iCal export & skipping entries

Hi, Following up on this, I've been looking in the source code. It seems that both :noexport: tags and ~org-icalendar-exclude-tags~ should be excluded from export according to ox-icalendar.el: https://github.com/emacsmirror/org/blob/master/lisp/ox-icalendar.el#L77 And more on line 258

Re: [O] Lower-casing blocks and keywords

Ignore previous email. Slightly misread your request. Not as trivial... ;-) -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-352-g92176c signature.asc Description: PGP signature

Re: [O] Lower-casing blocks and keywords

On Wednesday, 24 Jan 2018 at 15:21, Kaushal Modi wrote: > Did you do that lower-casing by hand? Or do you have an elisp snippet or > some script that does that? I have no idea how Nicolas did the changes but, remember, org has the full power of Emacs behind it (it's all text ;-)) so a simple

[O] Lower-casing blocks and keywords

Hello Nicolas, I also like the blocks and keywords to be lower-cased. I see this in the latest commit on master: https://code.orgmode.org/bzg/org-mode/commit/13424336a6f30c50952d291e7a82906c1210daf0 Did you do that lower-casing by hand? Or do you have an elisp snippet or some script that does

Re: [O] Fwd: asynch ical export

Hi Nicolas, On 2018-01-24 at 13:31, Nicolas Goaziou wrote: > Ken Mankoff writes: >> If I evaluate (org-icalendar-combine-agenda-files t) the target ics >> file is not updated, but it is if I change 't' to 'nil'. When I run >> that from the command line

Re: [O] Fwd: asynch ical export

Hello, Ken Mankoff writes: > When I try asynchronous ical export via (org-icalendar-combine-agenda-files > t), it does not appear to work. I'm using org 9.1.6. > > If I evaluate (org-icalendar-combine-agenda-files t) the target ics file is > not updated, but it is if I

Re: [O] [feature] prepend comment char before org-babel-ref

Hello, "numbch...@gmail.com" writes: > I think this function should be in Org-mode itself. > Because when you're editing the source code, will not want this src-coderef > like `(ref:example)` be editable. It should be in comment. Thank you for the suggestion. However I

Re: [O] [RFC] Moving "manual.org" into core

Hello, Yasushi SHOJI writes: > How about using org-lint or some other formatter on git commit hook? > after go lang introduced gofmt, many projects adapted the method to > keep the code constant. Org Lint is not a formatter. It detects common mistakes or hypothetical

[O] Fwd: asynch ical export

Hi List, [Apologies if you get this 2x. I got the first one bounced back claiming the list address did not exist] When I try asynchronous ical export via (org-icalendar-combine-agenda-files t), it does not appear to work. I'm using org 9.1.6. If I evaluate (org-icalendar-combine-agenda-files

Re: [O] [RFC] Moving "manual.org" into core

Hi, On Mon, Jan 22, 2018 at 10:54 PM, Rasmus wrote: > Bastien Guerry writes: > >> I'm all for editing manual.org instead of org.texi in the long run. >> >> Before moving manual.org into doc/, I'd suggest we agree on editing >> variables like `fill-column' and the