Re: org-deadline-warning-days per file
> Nick Dokos writes: > Colin Baxter writes: >> I have my org-deadline-warning-days set to 60 via >> >> #+begin_src elisp (setq org-deadline-warning-days 60) #+end_src >> >> in my ~/.emacs. How can I set it individually for each deadline >> in an org-mode file? >> > The manual says: > , | You can specify a different lead time for warnings for a > specific | deadlines[sic] using the following syntax. Here is an > example with a | warning period of 5 days ‘DEADLINE: <2004-02-29 > Sun -5d>’. This | warning is deactivated if the task gets > scheduled and you set | > ‘org-agenda-skip-deadline-prewarning-if-scheduled’ to ‘t’. ` Thank you. Read the manual? Now that's a revolutionary idea I'll adopt as my New Year resolution. Best wishes, -- Colin Baxter www.Colin-Baxter.com
Re: org-deadline-warning-days per file
Colin Baxter writes: > I have my org-deadline-warning-days set to 60 via > > #+begin_src elisp > (setq org-deadline-warning-days 60) > #+end_src > > in my ~/.emacs. How can I set it individually for each deadline in an > org-mode file? > The manual says: , | You can specify a different lead time for warnings for a specific | deadlines[sic] using the following syntax. Here is an example with a | warning period of 5 days ‘DEADLINE: <2004-02-29 Sun -5d>’. This | warning is deactivated if the task gets scheduled and you set | ‘org-agenda-skip-deadline-prewarning-if-scheduled’ to ‘t’. ` HTH. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: Wholesale changes to LaTeX headers
Norman Walsh writes: If you want these changes globally, I would start with the org-latex-classes variable. There is a lot you can do by tweaking the values in this variable. I found the documentation to be good, but dense (i.e. a lot to it, needing a git to digest fully). The docs for that variable will also point you to other variables you can tweak to do what you want. If you just want to tweak for specific files, #+LATEX_HEADER and #+LATEX_HEADER_EXTRA might be sufficient. I find these a good place to experiment with different settings. If they prove more widely useful, I will transfer/translate them into the other org-latex variables. Finally, doing an M-x apropos for org-latex-.* will likely bring up some additional variables which my be of interest/use. Tim > Hi, > > I want to make wholesale changes to the LaTeX preamble exported from > Org mode. I want to put \RequirePackage and \PassOptionsToPackage > calls before the \documentclass, I want to write a specific set of > macros after the \documentclass, I want to craft a couple of > \renewcommands, etc. > > Where should I begin? > > Be seeing you, > norm -- Tim Cross
Re: Wholesale changes to LaTeX headers
> On Dec 31, 2019, at 7:42 AM, Norman Walsh wrote: > > Hi, > > I want to make wholesale changes to the LaTeX preamble exported from > Org mode. I want to put \RequirePackage and \PassOptionsToPackage > calls before the \documentclass, I want to write a specific set of > macros after the \documentclass, I want to craft a couple of > \renewcommands, etc. > > Where should I begin? Execute this src block: #+begin_src emacs-lisp :results none (info "(org) LaTeX header and sectioning") (describe-variable 'org-latex-classes) #+end_src Browse the *info* buffer and study the *Help* buffer. Then type `M-x customize-variable RET org-latex-classes RET` and add your custom class or modify an existing class to your liking. HTH, Chuck
Wholesale changes to LaTeX headers
Hi, I want to make wholesale changes to the LaTeX preamble exported from Org mode. I want to put \RequirePackage and \PassOptionsToPackage calls before the \documentclass, I want to write a specific set of macros after the \documentclass, I want to craft a couple of \renewcommands, etc. Where should I begin? Be seeing you, norm -- Norman Walsh | The stone fell on the pitcher? Woe to http://nwalsh.com/| the pitcher. The pitcher fell on the | stone? Woe to the pitcher.--Rabbinic | Saying signature.asc Description: PGP signature
Re: problem with org-toggle-inline-images
Nicolas Goaziou writes: > Hello, > > Marco Wahl writes: > >> A natural fix is committed, I think. Would be great if you could test >> this fix. > > Thank you for the fix. > > Could you refactor it so belongs to org-compat.el? For example, we could > create image-map keymap there if Emacs < 26. Okay, I make a TODO out of this and try to work on the task soon. Right now I'm on my way outside... :) Ciao
Re: Bug: C-c C-k show branches also expands archived headings [9.3.1 (9.3.1-elpaplus @ /home/ionasal/.emacs.d/elpa/org-plus-contrib-20191226/)]
Allen Li writes: > The command org-kill-note-or-show-branches bound to C-c C-k when used to > show branches also expands headings tagged with :ARCHIVE:. This is > contrary to expectations, as the manual states: > > ‘C-c C-k’ (‘outline-show-branches’) > Expose all the headings of the subtree, CONTENTS view for just one > subtree. > > CONTENTS view when using TAB cycling does not expand archived headings. > > Can be reproduced with a .org file containing: > > * Foo > ** Bar :ARCHIVE: > *** Baz > > Emacs : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) > of 2019-08-29 > Package: Org mode version 9.3.1 (9.3.1-elpaplus @ > /home/ionasal/.emacs.d/elpa/org-plus-contrib-20191226/) Please check out the git heads or a future Org vorsion for the fix. Thanks.
Re: problem with org-toggle-inline-images
Hello, Marco Wahl writes: > A natural fix is committed, I think. Would be great if you could test > this fix. Thank you for the fix. Could you refactor it so belongs to org-compat.el? For example, we could create image-map keymap there if Emacs < 26. Regards, -- Nicolas Goaziou
Re: problem with org-toggle-inline-images
Johannes Brauer writes: > Typing C-c C-x C-v the image is displayed in the org buffer > correctly. Typing C-c C-x C-v again the image does not disappear and I > get the error message: > > org-toggle-inline-images: Symbol’s value as variable is void: image-map > > Any hints what is going wrong? > > I am using > Aquamacs 3.5 GNU Emacs 25.3.50.1 (x86_64-apple-darwin16.7.0, NS > macOs 10.15.2 > Org mode version 9.3 (9.3-8-geab7c4-ELPA IIUC variable image-map was introduced with Emacs 26. This looks like a good explanation of the behavior in your environment. A natural fix is committed, I think. Would be great if you could test this fix. If you want to use the image key map to rotate and zoom inline images in Org you need to upgrade to Emacs 26, though. Thanks again and best regards.
Re: using #+ to define faces
> On Dec 31, 2019, at 18:57, Nicolas Goaziou wrote: > > Hello, > > Jean-Christophe Helary > writes: > >> I would like to define faces on a file basis by using #+ but I'm not >> finding relevant info in the manual. >> >> Is it possible ? > > You may be able to set faces using file-local variables (info > "(emacs)File Variables"), but I haven't checked. Thank you Nicolas, I'll check later. Jean-Christophe Helary --- http://mac4translators.blogspot.com @brandelune
Re: orgalist-mode: wrong indentation in message mode after recent change in emacs
Hello, "Basil L. Contovounesios" writes: > Yes. :) I think the patch I proposed in my previous email should be > applied to orgalist, as a first step at the very least. Yay! 35 weeks later, but still before the coming year, I applied your patch to Orgalist code base. Thank you. Happy New Year, -- Nicolas Goaziou
Re: using #+ to define faces
Hello, Jean-Christophe Helary writes: > I would like to define faces on a file basis by using #+ but I'm not > finding relevant info in the manual. > > Is it possible ? You may be able to set faces using file-local variables (info "(emacs)File Variables"), but I haven't checked. Regards, -- Nicolas Goaziou
Re: Include file relative path
Hello, Steven Penny writes: > The Org Mode section on including files: > > https://orgmode.org/manual/Include-files.html > > seems to be missing a detail. It appears that relative paths are allowed, I > assume they would be relative to the directory of the parent file. Yes, see the last example in the section. > That is to say if I have file "monday.org" including file "sunday.org", and > they > are in the same folder, then I could use this syntax: > > #+INCLUDE: "sunday.org" > > Is that correct? Have you tried it? It looks correct. Otherwise, "./sunday.org" should work. Regards, -- Nicolas Goaziou
