Hi Nicolas,
maybe first have to get clear what you mean by "not accepting raw commands".
Would that mean that if I write \vspace in the buffer, the LaTeX exporter
would then give me \textbackslash{}vspace, for example, because i thinks that
I want that text to appear in the output?
- Carsten
On
Bastien writes:
> The patch is longer than 20 lines, so we would need you to sign the
> FSF papers to be able to accept it.
Request submitted.
--
Jarmo
Achim Gratz writes:
> Well, it doesn't become a TINYCHANGE just because you put that stamp
> on it. This patch clearly is over 20 non-trivial lines, so you will
> need to assign copyright to the FSF.
The program code (one macro and two calls) is less than 20 lines, and I
was hoping documentatio
>> I tested the new functions locally, as can be seen from the
>> examples. I also ran make without problems. I am, however, unable to
>> install org from the git version (for some unknown reason), so I was
>> unable to test the final, committed version.
>
> I can't decode that last part… you inst
Clément Mayet writes:
> *I think the main difficulty is to get the project to which the action
> belongs as it is only a heading above the action. My first question is
> : should I use properties, tags , something else ?*
I use properties for projects.
Depending on your numbers of concurrent pro
Robert Horn writes:
> *** HABIT [#A] Weekly GTD review [0/9]
> :home:
> DEADLINE: <2012-09-21 Fri ++1w> SCHEDULED: <2012-09-17 Mon ++1w>
> :LOGBOOK:
> - State "DONE" from "HABIT" [2012-09-14 Fri 09:00]
> I thought that it should be
Hello,
Just a Git question that puzzles me for long about how to send commits per
email to Org ML?
In the documentation (http://orgmode.org/worg/org-contribute.html), it's
written:
#+begin_src sh
git commit -m "Your message"
git format-patch master
#+end_src ^^
When I follow it
Hello,
Carsten Dominik writes:
> maybe first have to get clear what you mean by "not accepting raw commands".
> Would that mean that if I write \vspace in the buffer, the LaTeX exporter
> would then give me \textbackslash{}vspace, for example, because i thinks that
> I want that text to appear i
Hello,
Eric Schulte writes:
> Does this problem present itself when you execute the inline code block
> interactively, or only when using the new latex exporter? If the later
> then it is a latex exporter bug and not a Babel bug. I've updated the
> subject line so that hopefully the latex expo
On 20 sep. 2012, at 13:57, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> maybe first have to get clear what you mean by "not accepting raw commands".
>> Would that mean that if I write \vspace in the buffer, the LaTeX exporter
>> would then give me \textbackslash{}vspace, f
2012/3/31 Nicolas Girard :
>
> when browsing my TODO items in the agenda, I wish I could display then
> in an indirect buffer.
> But as I structure my stuff, displaying the tree with a TODO item as
> root is often useless.
>
> Indeed, within my PROJECT items, I differentiate between TODO and
> supp
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > Loris Bennett wrote:
>> >> In the *Org-Babel Error Output* buffer, I get the following:
>> >>
>> >> /bin/bash: /scpc:x@xx:/tmp/sh-script-7472puH: No such file or
>> >> directory
>>
>> It would seem that you are tryi
Sorry for not reading the docs carefully enough.
I had overlooked :results wrap
But even with this options things behave strangely.
src_emacs-lisp[:results wrap]{(+ 2 3)} :RESULTS:
5:END:
:RESULTS:
5:END:
:RESULTS:
5:END:
:RESULTS:
5:END:
:RESULTS:
5:END:
Running the code multiple times in the d
Thanks Anthony. Looks like that will be helpful if I ever update.
Memnon Anon writes:
>
> I think the consistency bar is only fully functional with timestamps
> of the format <2012-09-13 Do .+7d/10d> : You need a minimum/maximum range.
>
Thank you. That was the clue I needed. I hadn't made the connection
between schedule repeat intervals and deadlines in hab
Hi,
I am having similar problems with LaTeX export. I am exporting source
code snippets (XML) which has many variables with underscores in their
names. At some point in the process of switching to more recent Org
the export started producing incorrect LaTeX so the generation of PDF
fails, therefor
Nicolas Goaziou writes:
> Hello,
>
> Eric Schulte writes:
>
>> Does this problem present itself when you execute the inline code block
>> interactively, or only when using the new latex exporter? If the later
>> then it is a latex exporter bug and not a Babel bug. I've updated the
>> subject l
Loris Bennett wrote:
> I used to be able do all sorts of stuff with sh, Perl and R. Now the
> following example no longer works:
>
> ,---
> | #+begin_src sh :dir /@:/tmp
> | echo "Executed by `whoami` on `hostname` in `pwd`"
> | #+end_src
Neuwirth Erich writes:
> Sorry for not reading the docs carefully enough.
> I had overlooked :results wrap
> But even with this options things behave strangely.
>
> src_emacs-lisp[:results wrap]{(+ 2 3)} :RESULTS:
> 5:END:
> :RESULTS:
> 5:END:
> :RESULTS:
> 5:END:
> :RESULTS:
> 5:END:
> :RESULTS:
Nick Dokos wrote:
> Loris Bennett wrote:
>
> > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > following example no longer works:
> >
> > ,---
> > | #+begin_src sh :dir /@:/tmp
> > | echo "Executed by `whoami` on
Hi Jarmo
On Wed, Sep 19, 2012 at 6:48 PM, Jarmo Hurri wrote:
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -2399,6 +2399,7 @@ formula, moving these references by arrow keys
> * Formula syntax for Lisp:: Writing formulas in Emacs Lisp
> * Durations and time values:: How to compute duratio
On 12-Sep-19, at 4:52 PM, Nick Dokos wrote:
> Anthony Lander wrote:
>
>>
>> On 12-Sep-19, at 2:10 PM, Nick Dokos wrote:
>>
>>> Bastien wrote:
>>>
Yes -- we'll never say it enough: don't use filladapt.el with org-mode.
>>>
>>> It's probably worth adding a paragraph about this in the or
Hello,
Eric Schulte writes:
> Thanks for finding the source of this problem. The preceding character
> is checked so that inline source blocks can be commented. E.g., a user
> may want =src_sh{date}= to appear verbatim.
=src_sh{date}= won't be expanded by `org-babel-exp-non-block-elements'
(i
Hi,
I think you're still on master when you make your changes.
git maintains your *local copy* of master as 'master', whereas the
original, unchanged upstream branch master is still available as
'origin/master'. You create a patch against a different branch, and
since you are on 'master' which
Nick Dokos wrote:
> Nick Dokos wrote:
>
> > Loris Bennett wrote:
> >
> > > I used to be able do all sorts of stuff with sh, Perl and R. Now the
> > > following example no longer works:
> > >
> > > ,---
> > > | #+begin_src sh :dir /@:/t
Nick Dokos wrote:
> I haven't chased it all the way down because the reverts are
> making my head spin, but it may be that somehow the above commit
> got lost somewhere - or it got fixed and then the big revert lost
> the fix. Maybe Eric or Bastien remembers what happened.
>
This doesn't make s
Nicolas Goaziou writes:
> Hello,
>
> Eric Schulte writes:
>
>> Thanks for finding the source of this problem. The preceding character
>> is checked so that inline source blocks can be commented. E.g., a user
>> may want =src_sh{date}= to appear verbatim.
>
> =src_sh{date}= won't be expanded by
Nick Dokos writes:
> Nick Dokos wrote:
>
>> I haven't chased it all the way down because the reverts are
>> making my head spin, but it may be that somehow the above commit
>> got lost somewhere - or it got fixed and then the big revert lost
>> the fix. Maybe Eric or Bastien remembers what happe
Bastien writes:
>> However I suggest to lose the plural
>> and just use `org-plus-contrib´.
>
> Yes, that's fine for me. Thanks,
Implemented and pushed.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentati
Jarmo Hurri writes:
> 2. When I tried to run "make test", it failed because I don't have ERT
>installed. I am running Emacs 23.3.1, which does not include ERT, and
>I could not find a package providing ert.el in the repositories of
>Fedora 16. Because I was running out of time, I decide
Thank you,
this clarified things for me!
I will look and suggest a place for mentioning this in the docs.
Erich
On Sep 20, 2012, at 4:23 PM, Neuwirth Erich wrote:
> Sorry for not reading the docs carefully enough.
> I had overlooked :results wrap
> But even with this options things behave str
Nick Dokos writes:
> This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> fixed somehow, either because of a revert or because some fix was
> actually applied, I don't know which. It was working until 7.8
Eric Schulte writes:
> Yea, that sounds reasonable, thanks for taking care of this. If I find
> time I'll dig through the mailing list and see if I can find the exact
> reason why that portion of the regexp was added.
That would be a great starting point to avoid repeating past mistakes.
> I'v
Achim Gratz wrote:
> Nick Dokos writes:
> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> > fixed somehow, either because of a revert or because some fix was
> > actually applied, I don't know
Hi,
Maybe I'm missing something obvious here, but I can't get org-e-groff to
generate anything but an empty output file. I've boiled this down to
the following minimal example. First save the attached example.org file
to /tmp/example.org. Then run the following in your shell,
# -*- shell-s
Nick Dokos writes:
> Achim Gratz wrote:
>
>> Nick Dokos writes:
>> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
>> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
>> > fixed somehow, either because of a revert or because some fix was
>> > actu
Achim Gratz wrote:
> Nick Dokos writes:
> > Achim Gratz wrote:
> >
> >> Nick Dokos writes:
> >> > This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> >> > me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> >> > fixed somehow, either because of a rever
Hi list,
I'm trying to setup org-wikinodes, and I have a directory with hundres of
org files and each of them has dozens+ nodes. It looks as if org-wikinode
can't build the wiki cache data-structure for that many files/nodes,
because it never finds the headlines. Am I missing something?
Thanks in
Hello guys,
My tag search is broken, for some reason. When I search for "tag1" for
example, the search breaks and I get the following message in the
*Messages* buffer:
if: Wrong type argument: stringp, ("tag0" "tag1" "tag3" "tag4")
Here's the backtrace:
Debugger entered--Lisp error: (wrong-type
At Wed, 19 Sep 2012 12:08:21 -0500,
Russell Adams wrote:
On Wed, Sep 19, 2012 at 09:15:35AM -0700, Eric Lubeck wrote:
> One of my particular concerns is this: I'm accustomed to using a
> chronological laboratory notebook for recording all of my data. The
> agenda views in org-mode seem to provide
Hey,
this is a nice idea and makes me wonder if it would be possible to use
templates to automatically commit all recent changes in a git repro,
and start a new day by a new fresh working space in git.
git links are already possible. The template could create a link to
the just checked in status i
At Fri, 21 Sep 2012 11:20:41 +0900,
Torsten Wagner wrote:
>
> Hey,
>
> this is a nice idea and makes me wonder if it would be possible to use
> templates to automatically commit all recent changes in a git repro,
> and start a new day by a new fresh working space in git.
> git links are already p
Hi there,
I find :clock-in not work in org-capture-templates, with initial empty heading:
(setq org-capture-templates
'(("j" "Journal" entry (file+datetree "")
"* %?\n%U\n%i\n" :clock-in t :clock-resume t)))
I proposed the patch:
Modified lisp/org-clock.el
diff --git a/
Marcelo de Moraes Serpa wrote:
> Hello guys,
>
> My tag search is broken, for some reason. When I search for "tag1" for
> example, the search breaks
> and I get the following message in the *Messages* buffer:
>
> if: Wrong type argument: stringp, ("tag0" "tag1" "tag3" "tag4")
>
> Here's the b
Nick Dokos wrote:
> What causes this is not clear however: check org.el:org-scan-tags to make
> sure that the call to org-agenda-format-item includes the level argument.
> That sounds unlikely however.
>
Geez - I'm doing a hash of things today. The scenario I was envisaging
was that org-agenda.
Thank you for the suggestion guys.
It looks as if most of the free solutions don't produce a very good output.
Prince does look very good, but it's way too much expensive. I think using
org and exporting to both HTML and learning just enough LaTeX in order to
export a well formatted output with a
Eric Schulte writes:
> "Arne Babenhauserheide (IMK)" writes:
>
>> Hi Eric,
>>
>> It’s much easier to answer, what this does not share with ob-ditaa.el :)
>>
>> If I cut out the obvious renaming (to be able to use a ditaa-exp
>> source type), it’s just this diff (and the first half of that only
>
>> --- a/doc/org.texi
>> +++ b/doc/org.texi
>> @@ -2399,6 +2399,7 @@ formula, moving these references by arrow keys
>> * Formula syntax for Lisp:: Writing formulas in Emacs Lisp
>> * Durations and time values:: How to compute durations and time values
>> * Field and range formulas::Fo
Updating to git HEAD solved the problem.
Thanks!
- Marcelo.
On Thu, Sep 20, 2012 at 10:36 PM, Nick Dokos wrote:
> Nick Dokos wrote:
>
> > What causes this is not clear however: check org.el:org-scan-tags to make
> > sure that the call to org-agenda-format-item includes the level argument.
> >
Hi Jarmo
On Fri, Sep 21, 2012 at 7:44 AM, Jarmo Hurri wrote:
> Ok. I guess this also means changing the (next,prev,up) parts of
> @node-commands.
Yes.
> Do you want me to make the change and submit a new patch?
Yes please, I suggest to wait a bit if there will be more comments.
Michael
50 matches
Mail list logo
