Hi all,
I would like to have some TODO items, so that I can mark some tasks as
incomplete; however, I don't want them to appear in the agenda, so that
it's not too cluttered. Use case:
* Blog
** DONE Blog post idea 1
** TODO Blog post idea 2
I know about (setq org-agenda-todo-list-sublevels nil
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 here---start--
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 sensitive area. And if we think
that it is unpredictable and advise
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 (p
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 and advise people to stay off of it, we are
>>> better off r
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 maybe also html.
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
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 link over a macro is t
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
/FoO/
Example output
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 that seem like they could affect this
>
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 Price writes:
> >
> >> do we have a synt
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
function
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 small bits into the min
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/")
> (require 'org)
>
> (setq org-t
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
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 it than offering it in this state.
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
'((sequence "NOTE"
"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, e.g. =SITE= as the markup, and not the
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,
--
Nicolas Goaz
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,
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, should we?
>>
>> We cannot have a syntax fo
> 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 from
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 probably replace
> missing
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 various documents. I
have
(setq org-todo-keywords
'
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 instead); using o-b-get-heade
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 not being clear abou
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 sing
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.
Eric Schulte's filter for HTML small caps
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) predictable.
Is it necessarily broken?
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 late) it is staying within the
>> "schedul
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 have it do small caps i
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 to o-b-get-header
> a
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
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 org-todo-keywords
>>> '((sequence "NOTE" "APPT" "TODO" "F
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" "TODO" "FEEDBACK" "VERIFY" "|" "DONE"
>>
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"
> "DELEGATED" "CANCELLED")))
>
>
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 This
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 a
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 you. A minor comment f
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
>>> lines.
>>>
>>> In the example below the caching works fine fo
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 days excluded.
>
>
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" result-params) 'outpu
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
simASM.=SITE=.=STRATEGY=.=BUDGET=.=FIREREGIME=.=JOBID=.=ARRAYID=
#+END_VERBATI
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
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 other way round:
>>
>> I want the text, e.g. =SITE= as the ma
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
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 markup, and not the whole text as
> verba
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
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 so
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 interactive evaluation,
>> i.e. C-c C-c on t
>>> "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 ()
> (org-toggle-latex-fragment '(16))
> (
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 update-org-latex-f
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.
Rainer
>
> ?
>
> not per
#+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 moment...)- but how can I e
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 he
55 matches
Mail list logo