list/ob-R.el (org-babel-R-command-primary-prompt,
org-babel-R-evaluate-session): Former adds customizable prompt value
the latter utilizes it.
My R prompt looks like this "ℝ> ". Babel needs to know more how to
handle various situations so the
regex used in `org-babel-R-evaluate-session' to ident
Dnia 2014-08-22, o godz. 21:02:56
Subhan Michael Tindall napisał(a):
> > Doesn't this suggest that org-agenda-todo-ignore-with-date is
> > obsolete?
> It's functionality is subsumed by org-agenda-todo-ignore-timestamp
> all, yes. [...]
Well, except that it isn't. A quick experiment on my agenda
> -Original Message-
> From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org
> [mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On
> Behalf Of Marcin Borkowski
> Sent: Friday, August 22, 2014 11:54 AM
> To: emacs-orgmode@gnu.org
> Subject: Re: [O] org-agenda-todo-i
2014ko abuztuak 22an, Nicolas Goaziou-ek idatzi zuen:
>
> torys.ander...@gmail.com (Tory S. Anderson) writes:
>
>> I realize you were responding to Aaron on this, but for my own
>> education, how does on "apply"?
>
> "Please push your patch on master branch" is more explicit.
Pushed.
Thanks,
Dnia 2014-08-22, o godz. 20:56:50
Marcin Borkowski napisał(a):
> #+LATEX_HEADER: \author[short-author]{Really \\long \\author}
> #+LATEX_HEADER: \newcommand{\author}[2][]{}
Oops, my bad. Actually, it should be \renewcommand. (Though I didn't
test this idea.)
Best,
--
Marcin Borkowski
http:/
Hi,
in the agenda we can mark several entries for bulk processing. In the
following example, the second and third agenda entries are marked. To
indicate they are marked, a '>' symbol is shown right before them:
Projects: TODO Write the document
> Projects: TODO Call Bob
> Projects: TODO A
Dnia 2014-08-22, o godz. 15:37:28
Nicolas Goaziou napisał(a):
> torys.ander...@gmail.com (Tory S. Anderson) writes:
>
> > I realize you were responding to Aaron on this, but for my own
> > education, how does on "apply"?
>
> "Please push your patch on master branch" is more explicit.
And befor
Dnia 2014-08-22, o godz. 15:41:34
Subhan Michael Tindall napisał(a):
> Try
> C-h v org-agenda-todo-ignore-with-date
> C-h v org-agenda-todo-ignore-timestamp
That's where I started;).
> There are substantial differences between the two.
> org-agenda-todo-ignore-with-date, when set, ignores all d
Nick Dokos writes:
> Sharon Kimble writes:
>
>>
>> ** WAITING Anise
>> CLOSED: [2014-08-20 Wed 10:29]
>>
>>
>> And only _waiting_ shows as closed, none of these other conditions do -
>>
>> #+TODO: TODO DONE NEXT IN-PROGRESS NOTES FIXME WAITING
>>
>> ...
>>
>> I think that the problems all stem f
Pascal Fleury writes:
> Please forget about the previous patch I submitted, I have a new one
> that should work now on all platforms.
> Let me know if it should be formatted differently.
You don't really want to fork into bash each time you're about to run a
shell code block just to find out if it
Nick Dokos writes:
> Nick Dokos writes:
>
>> Sebastien Vauban
>> writes:
>>
>>> Nick Dokos wrote:
Thorsten Jolitz writes:
> Thorsten Jolitz writes:
>
> As a side-remark, I did send these blocks with emptly lines between them,
> and when I look at my post in gmane the form
I have noticed a possible bug in the output of src blocks, especially
for emacs-lisp blocks.
This block works fine.
#+BEGIN_SRC emacs-lisp :results raw
'(nil ("a" . "b"))
#+END_SRC
#+RESULTS:
(nil (a . b))
This block however, gives me an error that is due to nil being the first
element of the
Try
C-h v org-agenda-todo-ignore-with-date
C-h v org-agenda-todo-ignore-timestamp
There are substantial differences between the two.
org-agenda-todo-ignore-with-date, when set, ignores all dates, and overrides
org-agenda-todo-ignore-{scheduled|deadline}
org-agenda-todo-ignore-timestamp is more co
Couple of weeks ago, I accidentally spammed the message board with several
attempts to send up a couple of patches for some problems I was seeing.
So, firstly, apologies for the spam.
The two problems I was seeing were related to executing js using node.js,
and exporting css with vendor propertie
Nicolas Richard writes:
> Thorsten Jolitz writes:
>> Maybe they switched to the new parser between versions, that parses a
>> src-block with :post-blank's, but does not take them into account when
>> interpreting?
>
> I tried an experiment : (defun org-mode (&rest _) t) and refresh. The
> newli
On Friday, 22 Aug 2014 at 15:51, Bastien wrote:
> Hi Eric,
>
> Eric S Fraga writes:
>
>> changes made on 28 July, commit 5512bedee, breaks insert diary
>> functionality. In particular, "i d" in the agenda inserts the new entry
>> in the wrong place in a date-tree diary org file.
>>
>> Reverting th
Hi list,
what is the difference between these two options?
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
Nicolas Richard writes:
> Thorsten Jolitz writes:
>> Maybe they switched to the new parser between versions, that parses a
>> src-block with :post-blank's, but does not take them into account when
>> interpreting?
>
> I tried an experiment : (defun org-mode (&rest _) t) and refresh. The
> newli
Nicolas Richard writes:
> I would like to blame (mm-uu-dissect) but I didn't look into it.
I now blame (mm-uu-dissect). The following patch fixes it, but that part
of the code must be there for a reason... and I don't know what it is.
Modified lisp/gnus/mm-uu.el
diff --git a/lisp/gnus/
Marcelo de Moraes Serpa writes:
> @Achim Thanks - replacing (require 'org-install) with (require
> 'org-loaddefs) solved the issue!
What about removing (require 'org-loaddefs) altogether?
--
Bastien
Nick Dokos writes:
> OK - glad it's working. It was a pretty weird bug.
Thanks for taking care of this!
--
Bastien
Rasmus writes:
>> Is there something wrong in what I am doing or is there a problem?
>
> I don't think there is a code bug. There is a potentially a
> documentation bug in the first line of the doc string you mentioned.
Indeed, this is a documentation bug -- can one of you provide a
patch for i
Hi Eric,
Eric S Fraga writes:
> changes made on 28 July, commit 5512bedee, breaks insert diary
> functionality. In particular, "i d" in the agenda inserts the new entry
> in the wrong place in a date-tree diary org file.
>
> Reverting this commit fixes the problem.
Reverted, thanks for reportin
Thorsten Jolitz writes:
> Maybe they switched to the new parser between versions, that parses a
> src-block with :post-blank's, but does not take them into account when
> interpreting?
I tried an experiment : (defun org-mode (&rest _) t) and refresh. The
newlines didn't come back (but fontificat
Hi Samuel,
Samuel Loury writes:
> I would like to provide a very tiny change in the regexp matching a
> beginning of table in org-table.el.
Applied in master, thanks,
--
Bastien
Nicolas Goaziou writes:
> AFAIK, [:space:] is not compatible with XEmacs.
FWIW, I'm less and less sure why we should worry about XEmacs
compatibility. I wish some XEmacs user could step up and take
care of all these XEmacs compatibility issue.
--
Bastien
Thorsten Jolitz writes:
> Nick Dokos writes:
>
>> Nick Dokos writes:
>>
>>> Sebastien Vauban
>>> writes:
>>>
Nick Dokos wrote:
> Thorsten Jolitz writes:
>> Thorsten Jolitz writes:
>>
>> ...
>> Am I the only one seeing this? Bug in gnus/message mode?
>
> I see
Hi Nicolas,
thanks for implementing this.
Nicolas Goaziou writes:
> Nicolas Berthier writes:
>
>> Indeed. I fixed it in the new attached patch. Thanks.
>
> Applied. Thank you.
Since the patch has been applied, I get a "Not at a block" error
when finding some org-mode files -- I'll investiga
torys.ander...@gmail.com (Tory S. Anderson) writes:
> I realize you were responding to Aaron on this, but for my own
> education, how does on "apply"?
"Please push your patch on master branch" is more explicit.
Regards,
Nicolas Richard writes:
> Nick Dokos writes:
>> One machine is running Gnus v. 5.13: that one smooshes the code
>> blocks together.
>>
>> The other is running Ma Gnus v. 0.12: that one leaves empty
>> lines between blocks.
>
> Do they both fontify blocks ?
Yes.
--
Nick
I realize you were responding to Aaron on this, but for my own education, how
does on "apply"?
Nicolas Goaziou writes:
> Hello,
>
> Aaron Ecay writes:
>
>> You’re right...I inadvertently tested the proposed solution with the
>> latex backend, but it turns out there’s a small difference between
Hello,
Nicolas Berthier writes:
> Indeed. I fixed it in the new attached patch. Thanks.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
Charles Millar writes:
> I have the following in a file that I export to LaTeX
>
> #+LATEX_CLASS: mysetup
> #+LATEX_HEADER: \newcommand{\RATE}{65.00}
>
> mysetup class
>
> (add-to-list 'org-latex-classes
> '("mysetup"
> "\\documentclass[11pt,letterpaper,oneside]{scrartcl}
> \
Hello,
Aaron Ecay writes:
> You’re right...I inadvertently tested the proposed solution with the
> latex backend, but it turns out there’s a small difference between how
> the latex and beamer backends calculate their \author. I think both
> backends should behave identically here and that the
Nick Dokos writes:
> Nick Dokos writes:
>
>> Sebastien Vauban
>> writes:
>>
>>> Nick Dokos wrote:
Thorsten Jolitz writes:
> Thorsten Jolitz writes:
>
> As a side-remark, I did send these blocks with emptly lines
> between them,
> and when I look at my post in gmane th
Hello,
I have a little patch (attached) that does check the version of bash, and
uses associative arrays (or doesn't) depending on that version.
The problem now is that the test suite will only work on one platform t a
time, i.e. if there is a bash4 there, it will pass, but if it has bash3, it
wi
36 matches
Mail list logo
