[O] resize png in org-toggle-latex-fragment

Hello I am using GNU emacs 25.0.50, and 8.3.1. The png generated ny org-toggle-latex-fragment are too small for my taste. I found two solutions http://emacs.stackexchange.com/questions/3387/how-to-enlarge-latex-fragments-in-org-mode-at-the-same-time-as-the-buffer-text (defun

Re: [O] Markup (=, ~) in word?

On Thu, Oct 29 2015 at 5:07:55 pm EEST, Rainer M Krug wrote: > Göktuğ Kayaalp writes: > >> On Thu, Oct 29 2015 at 2:21:17 pm EEST, Rainer M Krug >> wrote: >>> Matt Price writes: >>> #+BEGIN_VERBATIM

Re: [O] problems with export and :cache

Hi Andreas, 2015ko urriak 28an, Andreas Leha-ek idatzi zuen: > > Hi all, > > Andreas Leha writes: >> Hi all, >> >> babel's :cache seems to be ignored during export. At least on #+call >> lines. >> >> In the example below the caching works fine for

Re: [O] [PATCH] Prevent overwriting of output files from babel calls with nil result

Hi Éibhear, I’m afraid I don’t understand the problem the patch is trying to fix. Can you provide a MWE (minimal working example) that illustrates the bug you’re observing? Thanks, -- Aaron Ecay

Re: [O] Markup (=, ~) in word?

On Thu, Oct 29 2015 at 2:21:17 pm EEST, Rainer M Krug wrote: > Matt Price writes: > >> #+BEGIN_VERBATIM >> simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= >> #+END_VERBATIM > > The other way round: > > I want the text, e.g. =SITE= as the

Re: [O] Markup (=, ~) in word?

Göktuğ Kayaalp writes: > On Thu, Oct 29 2015 at 2:21:17 pm EEST, Rainer M Krug > wrote: >> Matt Price writes: >> >>> #+BEGIN_VERBATIM >>> simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= >>> #+END_VERBATIM >> >> The

Re: [O] [PATCH] ob-python: Fix python session initialization

Hi Grégoire, I’ve looked at ‘org-babel-python-initiate-session’ and I can’t see an obvious bug. Did you come up with a patch to fix the problems you were seeing? Thanks, -- Aaron Ecay

Re: [O] problems with export and :cache

Hello, Aaron Ecay writes: > The simple patch attached to this message fixes a bug that my testing > indicated was responsible for erroneous re-evaluations at least some > of the time. Thank you. A minor comment follows. >(cons :result-type (cond ((member "output"

[O] TODO list with future scheduled events excluded

Dear all, with the TODO list view (org-todo-list) I get all my TODO entries, including the ones that are scheduled far in the future. This clutters up this view quite a bit, and I would prefer to have a TODO list with entries scheduled to future days excluded. Maybe miss something obvious, but

Re: [O] resize png in org-toggle-latex-fragment

>>> "Uwe" == Uwe Brauer writes: > Hello > I am using GNU emacs 25.0.50, and 8.3.1. > The png generated ny org-toggle-latex-fragment are too small for my > taste. > I found two solutions > (defun update-org-latex-fragments () >

Re: [O] Bug? Improper interaction with python variable _ ?

Hi Brian, 2015ko urriak 5an, Brian Beckman-ek idatzi zuen: > > Please see the gist below for a self-explaining example > copied here for convenience. Emacs 24.5.1 with org-mode > 8 something (not sure how to get it to report its exact > version)... a very late version, I am sure. Verified with

[O] Adding user-defined task state for agenda

I'm trying to add a NOTE state so that I can use agenda to quickly view a list of notes that I've embedded in various documents. I have (setq org-todo-keywords '((sequence "NOTE" "APPT" "TODO" "FEEDBACK" "VERIFY" "|" "DONE" "DELEGATED" "CANCELLED"))) in my .emacs, and I put ** NOTE

Re: [O] Adding user-defined task state for agenda

Kyle Meyer writes: > Peter Davis writes: > >> I'm trying to add a NOTE state so that I can use agenda to quickly view a >> list of notes that I've embedded in various documents. I >> have >> >> (setq org-todo-keywords >> '((sequence "NOTE" "APPT"

Re: [O] TODO list with future scheduled events excluded

Georg Otto writes: > Dear all, > > with the TODO list view (org-todo-list) I get all my TODO entries, > including the ones that are scheduled far in the future. This clutters > up this view quite a bit, and I would prefer to have a TODO list with > entries scheduled to future

Re: [O] problems with export and :cache

Hi Aaron, Aaron Ecay writes: > Hi Andreas, > > 2015ko urriak 28an, Andreas Leha-ek idatzi zuen: >> >> Hi all, >> >> Andreas Leha writes: >>> Hi all, >>> >>> babel's :cache seems to be ignored during export. At least on #+call >>>

Re: [O] problems with export and :cache

Hi Andreas, 2015ko urriak 29an, Andreas Leha-ek idatzi zuen: > Thanks a lot. I applied your patch but it seems that your patch does > not solve the problem in this specific situation. Or do I miss > something? That patch only solves one possible source of the problem. There are others, which

Re: [O] Adding user-defined task state for agenda

Peter Davis writes: > I'm trying to add a NOTE state so that I can use agenda to quickly view a > list of notes that I've embedded in various documents. I > have > > (setq org-todo-keywords > '((sequence "NOTE" "APPT" "TODO" "FEEDBACK" "VERIFY" "|" "DONE" >

Re: [O] problems with export and :cache

Hi Nicolas, 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: > > Hello, > > Aaron Ecay writes: > >> The simple patch attached to this message fixes a bug that my testing >> indicated was responsible for erroneous re-evaluations at least some >> of the time. > > Thank

[O] small caps

do we have a syntax for the "small caps" text attribute in Org? If not, should we? It is available in odt, html, and latex, and is used in some bibliographic styles. m

Re: [O] org-agenda-scheduled-leaders and repeating tasks

On Wed, Oct 28, 2015 at 9:52 AM, Nicolas Goaziou wrote: > cesar mena writes: > >> however the face is now `org-scheduled-today, as opposed to >> `org-scheduled-previously, and the agenda sorting is wrong. instead of >> bubbling to the top (since it is so

Re: [O] small caps

Hello, Matt Price writes: > do we have a syntax for the "small caps" text attribute in Org? No, we don't. > If not, should we? We cannot have a syntax for everything. A macro can probably replace missing syntax. Also, you can hijack some emphasis marker (e.g., "+") and

Re: [O] small caps

Aloha Aaron, Aaron Ecay writes: > Hi Nicolas, > > 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: >> >> Hello, >> >> Matt Price writes: >> >>> do we have a syntax for the "small caps" text attribute in Org? >> >> No, we don't. >> >>> If not,

Re: [O] problems with export and :cache

Hi Nicolas, 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: > Could these 2 use cases be refactored? > > (mapcar #'cdr (org-babel-get-header params :var)) > > is not very far (but stlightly different) from > > (cadr (org-babel-get-header params :colname-names)) > > when there is a

Re: [O] Adding user-defined task state for agenda

Kyle Meyer writes: > Peter Davis writes: > >> Kyle Meyer writes: >> >>> Peter Davis writes: >>> I'm trying to add a NOTE state so that I can use agenda to quickly view a list of notes that I've embedded in

Re: [O] small caps

Hi Nicolas, 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: > > Hello, > > Matt Price writes: > >> do we have a syntax for the "small caps" text attribute in Org? > > No, we don't. > >> If not, should we? > > We cannot have a syntax for everything. A macro can

Re: [O] problems with export and :cache

Andreas Leha writes: > Generally, I think that caching is a sensitive area. And if we think > that it is unpredictable and advise people to stay off of it, we are > better off removing it than offering it in this state. At least until > it behaves (more)

Re: [O] [PATCH] Prevent overwriting of output files from babel calls with nil result

> Hi Éibhear, > > I'm afraid I don't understand the problem the patch is trying to fix. > Can you provide a MWE (minimal working example) that illustrates the bug > you're observing? > > Thanks, > > -- > Aaron Ecay > Hi Aaron, Thanks for getting back to me. Prerequisites: - The dot utility

Re: [O] small caps

Aaron Ecay writes: > This is true. But small-caps are meaningful in a variety of contexts, > and they are not a truly new syntax (requiring extra code in the > parser), Of course they do. You need to introduce yet another emphasis marker. Regards,

Re: [O] Adding user-defined task state for agenda

Peter Davis writes: > Kyle Meyer writes: > >> Peter Davis writes: >> >>> I'm trying to add a NOTE state so that I can use agenda to quickly view a >>> list of notes that I've embedded in various documents. I >>> have >>> >>> (setq

Re: [O] problems with export and :cache

Aaron Ecay writes: > I’d like to remove this function, actually. I hate the org functions > that do X most of the time, but the opposite of X when you pass them > an optional argument (in this case the third arg ‘other’). > Almost all (a couple dozen in total) of the calls

Re: [O] small caps

Aloha Matt, Nicolas Goaziou writes: > Hello, > > Matt Price writes: > >> do we have a syntax for the "small caps" text attribute in Org? > > No, we don't. > I've been using this export filter, written by Eric Schulte. It works fine for my uses.

Re: [O] Markup (=, ~) in word?

On Thu, 29 Oct 2015, Rainer M Krug wrote: Matt Price writes: #+BEGIN_VERBATIM simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= #+END_VERBATIM The other way round: I want the text, e.g. =SITE= as the markup, and not the whole text as verbatim - sorry for

Re: [O] Adding user-defined task state for agenda

Peter Davis writes: [...] >> Can you reproduce it with emacs -Q and a minimal Org configuration? > > I'm not sure how to do that. You can put something like (add-to-list 'load-path "/path/to/your/org-mode/lisp/") (require 'org) (setq org-todo-keywords

Re: [O] Adding user-defined task state for agenda

Peter Davis writes: [...] > Hmmm. It worked in the minimal case, but still doesn't work in my > normal environment. Well that gives you something to go on. I'd recommend looking for parts of your normal Org configuration that seem like they could affect this and dumping

Re: [O] [PATCH] Prevent overwriting of output files from babel calls with nil result

Hi Éibhear, Thanks for sending the example. I think it is not expected to work going forward because the lisp block relies on being able to pick up the value of ‘params’, which will not be possible now that org is moving to lexical binding. In general, org-babel-execute:foo are internal

Re: [O] problems with export and :cache

Hi Nicolas, 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: > > Andreas Leha writes: > >> Generally, I think that caching is a sensitive area. And if we think >> that it is unpredictable and advise people to stay off of it, we are >> better off removing

Re: [O] Adding user-defined task state for agenda

Kyle Meyer writes: > Peter Davis writes: > > [...] > >>> Can you reproduce it with emacs -Q and a minimal Org configuration? >> >> I'm not sure how to do that. > > You can put something like > > (add-to-list 'load-path "/path/to/your/org-mode/lisp/") >

Re: [O] Markup (=, ~) in word?

"Charles C. Berry" writes: > On Thu, 29 Oct 2015, Rainer M Krug wrote: > >> Matt Price writes: >> >>> #+BEGIN_VERBATIM >>> simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= >>> #+END_VERBATIM >> >> The other way round: >> >> I want the text,

Re: [O] problems with export and :cache

Hi Nicolas, 2015ko urriak 29an, Aaron Ecay-ek idatzi zuen: >> Using `loop' here is, IMO, over-doing it. You can use instead, e.g., >> >> (org-remove-if >> (lambda (item) >> (memq (car item) >> '(:colname-names :rowname-names :result-params :result-type :var))) >> params) > > OK. I’ll push this

Re: [O] small caps

Tom, Am I right that this should turn {sc hello} into hello ? If so, it doesn't seem to be working for me so far. Thanks, m On Thu, Oct 29, 2015 at 12:55 PM, Thomas S. Dye wrote: > Aloha Matt, > > Nicolas Goaziou writes: > > > Hello, > > > > Matt

Re: [O] Adding user-defined task state for agenda

Kyle Meyer writes: > Peter Davis writes: > > [...] > >> Hmmm. It worked in the minimal case, but still doesn't work in my >> normal environment. > > Well that gives you something to go on. I'd recommend looking for parts > of your normal Org configuration

Re: [O] Markup (=, ~) in word?

Rainer M Krug writes: > Hi > > I guess this is not possible (and has been asked before, but I can't > find it t the moment...)- but how can I export the following markup? > > simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= > > > Export will be mainly LaTeX, but

[O] Resolving links breaks workflow using org-narrow-to-subtree

Hi, I am using Org-mode version 8.3.2 (8.3.2-10-g00dacd-elpa) to organize my lecture notes and export them to LaTeX. The final PDF document is quite large (around 200 pages), so the corresponding org-file has a decent size as well. To make editing easier, I often narrow my org buffer down to the

Re: [O] small caps

Hi, Matt Price wrote: > do we have a syntax for the "small caps" text attribute in Org? If not, > should we? It is available in odt, html, and latex, and is used in some > bibliographic styles. You can add a link type, e.g.: #+begin_src emacs-lisp (org-add-link-type "fm" nil (lambda

Re: [O] small caps

Matt Price writes: > do we have a syntax for the "small caps" text attribute in Org? If not, > should we? It is available in odt, html, and latex, and is used in some I use the following filter(s) (second one is not essential). Example input: CO_2 fOO Fo1O

Re: [O] small caps

Aloha Matt, Matt Price writes: > Tom, > > Am I right that this should turn > {sc hello} > > into > > hello > > ? > > If so, it doesn't seem to be working for me so far. Thanks, > m Sorry, I forgot to give an example. I use it like this [[sc:ad][AD]]. The advantage of a

Re: [O] problems with export and :cache

Aloha all, Aaron Ecay writes: > Hi Nicolas, > > 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: >> >> Andreas Leha writes: >> >>> Generally, I think that caching is a sensitive area. And if we think >>> that it is unpredictable

Re: [O] problems with export and :cache

Hi Thomas, Thomas S. Dye writes: > Aloha all, > > Aaron Ecay writes: > >> Hi Nicolas, >> >> 2015ko urriak 29an, Nicolas Goaziou-ek idatzi zuen: >>> >>> Andreas Leha writes: >>> Generally, I think that caching is a

Re: [O] problems with export and :cache

Aaron Ecay writes: > But users know that anyway, since it’s implied by the semantics of > :colname-names. Actually the most typical way of accessing the value > of :colname-names in the code is (cdr (assoc :colname-names params)) > (~20 uses, which ought to use assq

Re: [O] small caps

Hello, Thomas S. Dye writes: > I use them in almost all my archaeology writing where it is conventional > to make AD, BC, and BP small caps. I assume you are using PDF output. You can modify `org-latex-text-markup-alist' or use #+MACRO: ad \textsc{ad} and so on. Regards,

[O] [babel] :eval and #+call lines

Hi all, Since this is not related to caching, I post this as a separate question from [1]. I want to argue that specifying ':eval never' as argument to a #+call line should transitively apply to the called block as well. Here is the example: --8<---cut

[O] Markup (=, ~) in word?

Hi I guess this is not possible (and has been asked before, but I can't find it t the moment...)- but how can I export the following markup? --8<---cut here---start->8--- simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= --8<---cut

Re: [O] Markup (=, ~) in word?

#+BEGIN_VERBATIM simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= #+END_VERBATIM ? not perfect, but... On Thu, Oct 29, 2015 at 7:06 AM, Rainer M Krug wrote: > Hi > > I guess this is not possible (and has been asked before, but I can't > find it t the

Re: [O] Markup (=, ~) in word?

Matt Price writes: > #+BEGIN_VERBATIM > simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID= > #+END_VERBATIM The other way round: I want the text, e.g. =SITE= as the markup, and not the whole text as verbatim - sorry for not being clear about what I want.