Re: [O] Updating org from git repository
James Harkins gmail.com> writes: > So, how do I solve the problem with org-version? I already sent an answer to your original question, but somehow that didn't make it to the list: most likely you've missed a "(require 'org-install)" in your startup sequence. Regards, Achim.
Re: [O] [BUG] new exporter and #+BEGIN_CENTER
Jambunathan K writes:
> Center within Src. I don't think you can nest the blocks.
>
It seems you are right. At least as far as executing the src block is concerned.
I was thinking along the lines of LaTeX's center environment, but I see
now that a src block within a CENTER didn't work with the old exporter
either.
> The cryptic message is org-export.el way of saying that there is a parse
> error or that the Org file doesn't to conform to schema.
The latest git pull gives no error - it just doesn't run the src block.
>
>> This throws an error:
>>
>> --
>> * headline 1
>>
>> #+BEGIN_CENTER
>>
>> #+BEGIN_SRC R :exports both
>> rnorm(10)
>> #+END_SRC
>>
>> #+END_CENTER
>> --
>>
>> M-: (org-export-to-buffer 'e-latex "latex buffer") RET
>>
>> It does not run the src block and the error is:
>>
>> (error "Invalid search bound (wrong side of point)")
>> re-search-forward("@@[-A-Za-z0-9]+:" 31 t)
>> [snip]
>> org-element-export-snippet-successor(31)
>> [rest deleted]
>>
>> Removing the whitespace between the BEGIN_CENTER and BEGIN_SRC lines
>> runs, but wrongly fails to execute the src block.
>>
>> Removing the CENTER results in running the src block and producing the
>> expected result.
>>
>> My last pull was yesterday: b7be665..69af091
>>
>> HTH,
>>
>> Chuck
--
Charles C. BerryDept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
Re: [O] Converting Org to Sweave (*.Rnw)
Julian Gehring writes: > Hi Chuck, > > thanks, what you describe seems to me like a already quite elaborated > solution. I would be very interested in your existing implementation > for this. > > As you mentioned, there will probably have to be a trade-off between > the syntax/functionality of Org-mode/babel and Sweave. But already a > solution being able to handle to obvious cases of header argumnets > would be step forward in bringing Org-mode even closer to R Sweave. > Julian, Please take a look at https://github.com/chasberry/orgmode-accessories and try it out. ravel.org implements a couple of backends to export to Sweave and brew style documents. There are commands embedded to create e-ravel.el, which powers the backends as well as commentary on how to implement some extensions. There are two POC *.org files which show some of the possibilities. Best, Chuck [snip]
Re: [O] Org mode export to Groff MM. Feature Freeze
On Tue, Jul 17, 2012 at 08:04:03PM -0400, Luis Anaya wrote: > > Man page >http://ppl.ug/G1D9Y4fIwXA/ > PDF >http://ppl.ug/1R5aCF_CmAE/ > Aboslutely amazing! Great job Luis. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] Org mode export to Groff MM. Feature Freeze
Nicolas Goaziou writes: All right fine... I went all crazy :) Centered text? Yes. Implemented centered block in man pages. This is probably one of the reasons the Org exporter enables the creation of complex typesetting. In this case, I'm using the .ce groff command to centralize the text. .ce requires the number of lines to centralized, provided by the content variable. It is not "dumb" markup translation. Tables? Yes. Man pages are groff files at the end. It can process TBL and EQN commands. You may need to configure man.conf to make sure that tbl and/or eqn is invoked. Multi levels? Yes, provided via .TP macros. The first two levels are using the headline macros from man. The next levels are through .TP and indentation. Bullet Lists? Yes, provided via .IP and using the different markers. Alpha lists? Are you kidding me?! NO! :) Ok, not yet. It should be possible to implement though. Links? The new version of the man command allows for URL and for Email. But I'm sticking mostly with legacy implementation in which they will be written out and that's it. For now... Want proof? Org file http://ppl.ug/6h0UFKJfm1c/ Man page http://ppl.ug/G1D9Y4fIwXA/ PDF http://ppl.ug/1R5aCF_CmAE/ Regards -- Luis R. Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] [BUG] new exporter and #+BEGIN_CENTER
Center within Src. I don't think you can nest the blocks.
The cryptic message is org-export.el way of saying that there is a parse
error or that the Org file doesn't to conform to schema.
> This throws an error:
>
> --
> * headline 1
>
> #+BEGIN_CENTER
>
> #+BEGIN_SRC R :exports both
> rnorm(10)
> #+END_SRC
>
> #+END_CENTER
> --
>
> M-: (org-export-to-buffer 'e-latex "latex buffer") RET
>
> It does not run the src block and the error is:
>
> (error "Invalid search bound (wrong side of point)")
> re-search-forward("@@[-A-Za-z0-9]+:" 31 t)
> [snip]
> org-element-export-snippet-successor(31)
> [rest deleted]
>
> Removing the whitespace between the BEGIN_CENTER and BEGIN_SRC lines
> runs, but wrongly fails to execute the src block.
>
> Removing the CENTER results in running the src block and producing the
> expected result.
>
> My last pull was yesterday: b7be665..69af091
>
> HTH,
>
> Chuck
--
Re: [O] [BUG] new exporter and #+BEGIN_CENTER
Hello,
cbe...@tajo.ucsd.edu writes:
> This throws an error:
>
> -- * headline 1
>
> #+BEGIN_CENTER
>
> #+BEGIN_SRC R :exports both
> rnorm(10)
> #+END_SRC
>
> #+END_CENTER
> --
>
> M-: (org-export-to-buffer 'e-latex "latex buffer") RET
>
> It does not run the src block and the error is:
>
> (error "Invalid search bound (wrong side of point)")
> re-search-forward("@@[-A-Za-z0-9]+:" 31 t)
> [snip]
> org-element-export-snippet-successor(31)
> [rest deleted]
>
> Removing the whitespace between the BEGIN_CENTER and BEGIN_SRC lines
> runs, but wrongly fails to execute the src block.
>
> Removing the CENTER results in running the src block and producing the
> expected result.
>
> My last pull was yesterday: b7be665..69af091
I cannot reproduce it, but I fixed something similar recently. You may
want to upgrade a try again.
Regards,
--
Nicolas Goaziou
[O] [BUG] new exporter and #+BEGIN_CENTER
This throws an error:
--
* headline 1
#+BEGIN_CENTER
#+BEGIN_SRC R :exports both
rnorm(10)
#+END_SRC
#+END_CENTER
--
M-: (org-export-to-buffer 'e-latex "latex buffer") RET
It does not run the src block and the error is:
(error "Invalid search bound (wrong side of point)")
re-search-forward("@@[-A-Za-z0-9]+:" 31 t)
[snip]
org-element-export-snippet-successor(31)
[rest deleted]
Removing the whitespace between the BEGIN_CENTER and BEGIN_SRC lines
runs, but wrongly fails to execute the src block.
Removing the CENTER results in running the src block and producing the
expected result.
My last pull was yesterday: b7be665..69af091
HTH,
Chuck
--
Charles C. BerryDept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
Re: [O] Updating org from git repository
On Tue, Jul 17, 2012 at 07:59:53PM +0200, Achim Gratz wrote: > Suvayu Ali writes: > > See the output of "make help". The above is not the prescribed way to do > > it. If you want the old make behaviour, you can do "make oldorg && make > > install". > > No, he's using the latest release version of Org, which means the old > Makefile (if this was really his intention I#d recommend to at least > check out maint). For your suggestion to work he'd need to switch to > the master branch. > Ah sorry. I misunderstood the OP. Thanks for correcting me. -- Suvayu Open source is the future. It sets us free.
Re: [O] Updating org from git repository
At Tue, 17 Jul 2012 17:37:09 -0400, Mehul Sanghvi wrote: > Did you have Emacs up and running already ? Did you restart Emacs ? Yes. I've even logged out and logged back in (for a separate reason). > Did you do M-x org-reload ? Quoting myself: ~~ Now, when I reload orgmode, the minibuffer correctly shows "Org-mode version 7.8.11 (release_7.8.11 @ /home/dlm/share/org-mode.git/lisp/)" ~~ The problem persists. hjh -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks
Re: [O] Updating org from git repository
On Tue, Jul 17, 2012 at 3:09 PM, James Harkins wrote: > Achim Gratz nexgo.de> writes: > >> Suvayu Ali writes: >> > See the output of "make help". The above is not the prescribed way to do >> > it. If you want the old make behaviour, you can do "make oldorg && make >> > install". >> >> No, he's using the latest release version of Org, which means the old >> Makefile (if this was really his intention I#d recommend to at least >> check out maint). For your suggestion to work he'd need to switch to >> the master branch. > > Indeed, "make help" just tells me to run "make install." > > So, how do I solve the problem with org-version? I use PDF export a lot during > the school year. > > hjh > > > Did you have Emacs up and running already ? Did you restart Emacs ? Did you do M-x org-reload ? cheers, mehul -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: [O] Feature that org mode needs most
On Tue, Jul 17, 2012 at 5:15 PM, Joseph Thomas wrote: > Hello. > I couldn't believe I hadn't been aware of org mode until a few months ago, > as someone who's been using emacs for everything for many years. > > I use it to journal how all my time is spent in a given work day- for both > work related tasks and non-work tasks (ex. getting coffee, lunch, > conversations, etc.). Org mode is the only GTD software package I've seen > that makes this possible without getting in the way. It just needs one > small thing that keeps it from being perfect. > > Those who use it the same way I do (as a log of how all time was spent in a > given day), there's no easy way I can see to make quick adjustments to > clocked time between activities. Every day I will forget to clock to a new > activity at some point. By the time I remember, time has passed. For > example, I come back from a meeting and begin to work on a project. 20 > minutes into it, I clock in. But I must then manually adjust both the > previous activity and the current one so that they are accurate and don't > overlap in the agenda view. This can be cumbersome, which seems to go > against the overall idea of org mode. All that is needed to correct it is > either a new fn and key binding, or a prefix arg to org-clock-in that allows > you to enter an adjustment (in this example, 20) to subtract from the > previous clock's out time and current clock's in time. > > Seems like it would be a minor thing to add that would make an enormous > difference for users like me. > > Thanks for reading my request! > > Regards, > Joe Joe, You can use the S-up and S-down key combinations to adjust the clocks for the current activity and the previous one. Move over to the hour and do S-up or S-down, then do the same with the minutes. The date gets adjusted automatically if you're straddling midnight. cheers, mehul p.s. does that make org-mode perfect now ? :) -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
[O] Feature that org mode needs most
Hello. I couldn't believe I hadn't been aware of org mode until a few months ago, as someone who's been using emacs for everything for many years. I use it to journal how all my time is spent in a given work day- for both work related tasks and non-work tasks (ex. getting coffee, lunch, conversations, etc.). Org mode is the only GTD software package I've seen that makes this possible without getting in the way. It just needs one small thing that keeps it from being perfect. Those who use it the same way I do (as a log of how all time was spent in a given day), there's no easy way I can see to make quick adjustments to clocked time between activities. Every day I will forget to clock to a new activity at some point. By the time I remember, time has passed. For example, I come back from a meeting and begin to work on a project. 20 minutes into it, I clock in. But I must then manually adjust both the previous activity and the current one so that they are accurate and don't overlap in the agenda view. This can be cumbersome, which seems to go against the overall idea of org mode. All that is needed to correct it is either a new fn and key binding, or a prefix arg to org-clock-in that allows you to enter an adjustment (in this example, 20) to subtract from the previous clock's out time and current clock's in time. Seems like it would be a minor thing to add that would make an enormous difference for users like me. Thanks for reading my request! Regards, Joe
Re: [O] implement appt warntime
I haven't had a look at the patch, but this property looks like a very nice and easy solution. +1. Ivan Kanis writes: > Hi Bastien, > > I had a look at org-notify.el. It's over engineered for my need. If you > recall I submitted a patch that added warntime on the header. It's not > pretty but it works for me. > > I could use properties instead. For example: > > ** an appointment with a reminder 5 minutes before 10:00 >SCHEDULED: <2012-07-16 Mon 10:00> > :PROPERTIES: > :WARNTIME: 5 > :END: > > Would you integrate such a functionality? I might code it if I find the > time. > > Take care, -- Moritz Ulrich
Re: [O] new exporter
Hello,
Achim Gratz writes:
> I used whatever I had pulled yesterday... again, that failure happens
> only with Emacs 23, which may well be a bug in that version or the
> particular build. It actually got worse in that I can't seem to find an
> eval limit that works today, so the corruption that backtraced yesterday is
> gone and I now have a truly infinite recursion apparently.
Would you happen to have any backtrace for them?
> The current test suite gives the following failure on Emacs 24, probably
> a fallout from the changes you did to the timestamp handling:
>
> 1 unexpected results:
>FAILED test-org-element/timestamp-interpreter
This should be fixed in a recent commit. I was quicker than the patrol
this time.
> Git will unlink them each time something changes at the original place
> and you are left with an inconsistent set of sources. You really need
> to remove and copy (or link) them each time you do a new checkout with
> Git; but add this to local.mk and make will do it for you each time you
> do a compile:
>
> compile::
> $(CP) contrib/lisp/org-{export,element,e-*}.el lisp/
> cleanall: cleanexporter
> cleanexporter:
> $(RM) lisp/org-{export,element,e-*}.{el,elc}
>
Noted. Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Rian Murphy yahoo.com> writes: Thanks everybody for your help with this problem. I am new to emacs and org-mode, and so a little tentative, but the support I got from this group is encouraging me to go further. I'm sure it's only a matter of time until org-mode gets me completely organized. Then the trouble will really start. Thanks again, Rian Murphy
Re: [O] Updating org from git repository
Achim Gratz nexgo.de> writes: > Suvayu Ali writes: > > See the output of "make help". The above is not the prescribed way to do > > it. If you want the old make behaviour, you can do "make oldorg && make > > install". > > No, he's using the latest release version of Org, which means the old > Makefile (if this was really his intention I#d recommend to at least > check out maint). For your suggestion to work he'd need to switch to > the master branch. Indeed, "make help" just tells me to run "make install." So, how do I solve the problem with org-version? I use PDF export a lot during the school year. hjh
Re: [O] Org mode export to Groff MM. Feature Freeze
Nicolas Goaziou writes: > One can imagine specialized back-ends only rendering a limited set of > Org features. As long as the set is explicitly documented in the > back-end, there's nothing wrong with that. Ok folks: I created an exporter for man page based on the groff one. It probably has more junk than my grandma's attic, and it was done more as a proof than anything else. Let me know what you guys think? Source: http://ppl.ug/IyI7M_Kt-3g/ Man Page: http://ppl.ug/YW6zXUs14FI/ PDF Result of Man Page http://ppl.ug/SlhZexxNHmA/ PDF Result with the MM macros (just for fun) http://ppl.ug/_RBFEzrEgzU/ Luis -- Luis R. Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Updating org from git repository
Suvayu Ali writes: > See the output of "make help". The above is not the prescribed way to do > it. If you want the old make behaviour, you can do "make oldorg && make > install". No, he's using the latest release version of Org, which means the old Makefile (if this was really his intention I#d recommend to at least check out maint). For your suggestion to work he'd need to switch to the master branch. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Nick Dokos writes: > In my case, make up2 installed into > > /usr/share/emacs/site-lisp/org You can always check what make thinks it should do via make config or even make config-all > (add-to-list 'load-path "/usr/share/emacs/site-lisp/org") That is not necessary, at least if subdirs.el already exists in /usr/share/emacs/site-lisp (Ubuntu should have it, but certain versions of Debian apparently don't - but you can copy the version from the Emacs installation). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] new exporter
Nicolas Goaziou writes:
>> 2 unexpected results:
>>FAILED test-org-element/parent-property
>>FAILED test-org-element/set-element
>
> I cannot get those. Have you tried with a recent Org (i.e. post
> 95cd07d058da79cb1767946dba6e4b9128a3a702)?
I used whatever I had pulled yesterday... again, that failure happens
only with Emacs 23, which may well be a bug in that version or the
particular build. It actually got worse in that I can't seem to find an
eval limit that works today, so the corruption that backtraced yesterday is
gone and I now have a truly infinite recursion apparently.
The current test suite gives the following failure on Emacs 24, probably
a fallout from the changes you did to the timestamp handling:
1 unexpected results:
FAILED test-org-element/timestamp-interpreter
Otherwise the same tests that are failing on Emacs 23 are clean on
Emacs 24.
>> ...but still not the error you've been reporting.
>
> I also cannot anymore. I suppose I had fumbled with hard links
> (i.e. forgetting to remove the previous one).
Git will unlink them each time something changes at the original place
and you are left with an inconsistent set of sources. You really need
to remove and copy (or link) them each time you do a new checkout with
Git; but add this to local.mk and make will do it for you each time you
do a compile:
--8<---cut here---start->8---
compile::
$(CP) contrib/lisp/org-{export,element,e-*}.el lisp/
cleanall: cleanexporter
cleanexporter:
$(RM) lisp/org-{export,element,e-*}.{el,elc}
--8<---cut here---end--->8---
If you want to switch back to a branch that doesn't use the new
exporter, remember to do a cleanall. BTW, I've added a description of
how to use multiple local.mk setups (for different Emacsen or different
test setups) on Worg.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] [new exporter] Bug: dates enclosed in angle brackets
Nicolas Goaziou writes: > Hello, > > Myles English writes: > >> A date entered with with C-c . exports without angle brackets in the old >> exporter but with angle brackets in the new exporter. I would have >> thought that without is preferable. > > Agreed. Brackets are only Org syntax. > > I have pushed a change about timestamp objects and planning elements. Thanks, it works. Myles
Re: [O] Converting Org to Sweave (*.Rnw)
Hi Chuck,
thanks, what you describe seems to me like a already quite elaborated
solution. I would be very interested in your existing implementation
for this.
As you mentioned, there will probably have to be a trade-off between the
syntax/functionality of Org-mode/babel and Sweave. But already a
solution being able to handle to obvious cases of header argumnets would
be step forward in bringing Org-mode even closer to R Sweave.
Best
Julian
On 07/17/2012 06:05 PM, cbe...@tajo.ucsd.edu wrote:
Julian Gehring writes:
Hi,
is there a way to convert Org-mode files with R code blocks to the
Sweave ('*.Rnw') [1] file format or has anyone planned to work on
this?
First, there is this thread:
http://comments.gmane.org/gmane.emacs.orgmode/7931
and then there is this
http://yihui.name/knitr/demo/org/
But I wanted more, and I think the new exporter provides some awesome
possibilities, so...
I have put together a rudimentary exporter for Sweave and for brew style
chunks and hope to have several of the knitr chunk flavors supported
soon. I've not looked closely, but I think pander can be supported, too.
The basic idea is to use the new export engine. See
http://orgmode.org/worg/dev/org-export-reference.html
for background.
The e-latex, e-html, and other modes are used as parent backends and
e-latex-rnw, e-html-brew, etc are *derived* backends. It is pretty easy
to hitch a ride on the work done to make a parent backend and then add a
minimal definition of the chunk formatting.
The only tricky bit is getting Babel to help in the process, but not
interfere. I want Babel to porcess non-R src blocks and clean out R
#+RESULTS blocks, but not strip out the header args, as these may be
wanted (as you suggest below) to inform the chunk arguments. I've
managed this by advise'ing org-babel-exp-do-export to do special
handling of R src blocks.
I've not yet delved into translating the headers into code chunk
arguments. Some like 'width' seem pretty obvious. Others like the
:exports + :results translation may take some thought. And there are
some idioms in Sweave and kntir that have not corresponding idiom in org
(which is a strong motive for doing this work) like 'dev' in knitr as
well as ':cache yes' versus 'cache=T', which are false cognates, so to
speak
So far, what I've done is do add a header arg like this:
Here is an inline chunk: src_R{ rnorm(1) } which the brew export
renders as <%= rnorm(1) -%> (i.e. print the result, but do not place
a line break after the result), making a non-printing version of this
is done by using this src_R[ :ravel <% -%> ]{ rnorm(1) }, which
renders as <% rnorm(1) -%>.
or this
: #+name: aCachedChunk
: #+begin_src R :ravel cache=T
: x <- rnorm(1e7)
: #+end_src
which is rendered as
<>=
x <- rnorm(1e7)
@ %def
when using the Sweave style exporters.
However, Nicolas *just* added support for #+ATTR_SOMETHING, where
SOMETHING is a user defined key. And I incline to the view that using
something like
: #+attr_ravel: cache=T
: #+name: aCachedChunk
: #+begin_src R
: x <- rnorm(1e7)
: #+end_src
might be preferred.
Anyway, I'll try to get a version up where you can have a look at it
sometime today.
I am keen to collaborate on this.
Chuck
Sweave is heavily used in the R community in terms of literate
programming, and has a tight integration into current package building
workflows. Essentially, the file format is a latex document, with
designated code chunks.
Since Org/Org-babel offers a very similar feature set, and already
covers the export to latex, I was wondering whether anyone is working
on some code that would rewrite the code block headers in the export?
In the R community, I have seen a lot of interest in such an exporter,
that would allow to write the documentation in Org itself and later
export it to several backends, including Sweave to integrate it in the
R package.
If anyone has some comments regarding this or is interested in working
on this, please let me know. My colleagues and I would be very
interested in contributing in projects in this direction.
Best
Julian
[1] http://en.wikipedia.org/wiki/Sweave
Re: [O] Remembrance Agent and Orgmode
Sadly I don't have any information to offer, but I'd like to second Karl's
request. I was also looking at the Remembrance Agent last week and trying to
figure out (1) how to get it properly set-up and (2) how it might best be used
in a "modern" Emacs(/Orgmode) setup.
Dr Benjamin Slade [ http://ling.uta.edu/~ben/ ]
Dept. of Linguistics & TESOL - University of Texas at Arlington
132E Hammond Hall | Office Hours: tba
Stæfcræft & Vyākaraṇa (lingblog) -
http://staefcraeft.blogspot.com
The Babbage Files (techblog) -
http://babbagefiles.blogspot.com
"While corporations dominate society and write the laws,
each advance in technology is an opening for them
to further restrict its users."
--Stallman's Law
Ongietan sceal gleaw hælehu gæstlic bið,
þonne ealre þisse worulde wela weste stondeð,
swa nu missenlicegeond þisne middangeard
winde biwauneweallas stondaþ,
hrime bihrorene, hryðge þa ederas.
--The Wanderer (73-77)
{sent from Emacs running under GNU/Linux}
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
John Hendy wrote: > On Tue, Jul 17, 2012 at 11:10 AM, Rian Murphy wrote: > > Christopher Witte witte.net.au> writes: > > > >> > >> On 17 July 2012 16:53, Rian Murphy yahoo.com> wrote: > >> > Giovanni Ridolfi yahoo.it> writes: > >> > ... > >> >> > I'd prefer to use capture on my Ubuntu installation. I searched the > >> >> > gmane > >> >> > archives and didn't find any clues. > >> >> > > ... > >> > >> Upgrading org is easy and there are instructions in the FAQ, > >> http://orgmode.org/worg/org-faq.html#updating-org > >> > >> Chris. > >> > >> > > Chris, thanks for your help. I should have looked in the org-mode > > FAQ to start with -- I apologize. > > Oddly, however, when I do a 'git pull' and a 'make up2', then restart > > emacs, 'org-version' still tells me I have version 6.30c. > > 'emacs-version' still says 23.1.50.1. > > Maybe it's a Ubuntu thing Thanks again, R.M. > > I've not used `make up2`, so I can't comment on how that's working. It > might help if you clearly listed the specific steps you used to get > orgmode from git. The Makefile in the main org directory pulls in targets.mk and in there you will find: , | ... | up0 up1 up2:: | git remote update | git pull | up1 up2:: all | $(MAKE) test-dirty | up2 update2:: | $(SUDO) $(MAKE) install | ... ` so ``make up2'' does the ``git pull'', runs the test suite and then runs ``make install'' (default.mk even sets SUDO, so the make install is run with superuser privileges :-) ). Nick
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Christopher Witte witte.net.au> writes: > > Chris, thanks for your help. I should have looked in the org-mode > > FAQ to start with -- I apologize. > > Oddly, however, when I do a 'git pull' and a 'make up2', then restart > > emacs, 'org-version' still tells me I have version 6.30c. > > 'emacs-version' still says 23.1.50.1. > > Maybe it's a Ubuntu thing Thanks again, R.M. > > > > I don't think it's an Ubuntu thing, I keep up to date with the git > repo under Ubuntu. Did you run 'make install'? You might need to run > 'sudo make install'. You should also be able to refresh org without > restarting emacs, I can't remember what the command is though. > > Fixed it. I had 'setq load-path cons' entries in my .emacs pointing to the wrong directories. I changed these, now it works beautifully. It's always those details that elude me Thanks for staying with me on this. R.M.
Re: [O] Updating org from git repository
On Tue, Jul 17, 2012 at 12:29:39PM -0400, James Harkins wrote: > I have done this: > > cd ~/share/org-mode.git > git checkout release_7.8.11 > git checkout -b rel7.8.11 > make > make install > See the output of "make help". The above is not the prescribed way to do it. If you want the old make behaviour, you can do "make oldorg && make install". -- Suvayu Open source is the future. It sets us free.
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
On Tue, Jul 17, 2012 at 11:10 AM, Rian Murphy wrote: > Christopher Witte witte.net.au> writes: > >> >> On 17 July 2012 16:53, Rian Murphy yahoo.com> wrote: >> > Giovanni Ridolfi yahoo.it> writes: >> > ... >> >> > I'd prefer to use capture on my Ubuntu installation. I searched the >> >> > gmane >> >> > archives and didn't find any clues. >> >> > ... >> >> Upgrading org is easy and there are instructions in the FAQ, >> http://orgmode.org/worg/org-faq.html#updating-org >> >> Chris. >> >> > Chris, thanks for your help. I should have looked in the org-mode > FAQ to start with -- I apologize. > Oddly, however, when I do a 'git pull' and a 'make up2', then restart > emacs, 'org-version' still tells me I have version 6.30c. > 'emacs-version' still says 23.1.50.1. > Maybe it's a Ubuntu thing Thanks again, R.M. I've not used `make up2`, so I can't comment on how that's working. It might help if you clearly listed the specific steps you used to get orgmode from git. My process, for example, is: - cd ~/.elisp - git clone http://orgmode.org/org-mode.git org.git - cd org.git - make clean && make && make doc I don't `make install`. You'll need to tell emacs where to run org from via your .emacs. Mine has this line: ,--- | (add-to-list 'load-path "~/.elisp/org.git/lisp") `--- Lastly, someone suggested I run this when I was having trouble getting org setup on my Mac with an out of date version despite having done the git thing: ,--- | M-x locate-library org `--- This will show you what path emacs *thinks* org is at, despite where you think it *should* be looking. ETA: I see some other emails came in. And yes, per Nick, make sure you set the load path *before* requiring org! I made that mistake once -- quite frustrating :) Good luck! John > > > >
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Rian Murphy wrote: > Christopher Witte witte.net.au> writes: > > > > > On 17 July 2012 16:53, Rian Murphy yahoo.com> wrote: > > > Giovanni Ridolfi yahoo.it> writes: > > > ... > > >> > I'd prefer to use capture on my Ubuntu installation. I searched the > > >> > gmane > > >> > archives and didn't find any clues. > > >> > ... > > > > Upgrading org is easy and there are instructions in the FAQ, > > http://orgmode.org/worg/org-faq.html#updating-org > > > > Chris. > > > > > Chris, thanks for your help. I should have looked in the org-mode > FAQ to start with -- I apologize. > Oddly, however, when I do a 'git pull' and a 'make up2', then restart > emacs, 'org-version' still tells me I have version 6.30c. > 'emacs-version' still says 23.1.50.1. > Maybe it's a Ubuntu thing Thanks again, R.M. > You probably don't have the installation directory in your load-path. Check with C-h v load-path RET. In my case, make up2 installed into /usr/share/emacs/site-lisp/org (afaik, that's the case with default values of ``prefix'' and ``DESTDIR'': the first one is "/usr/share" and the second is undefined in the default configuration). If that's the case with you as well, then you'd have to say (add-to-list 'load-path "/usr/share/emacs/site-lisp/org") before (require 'org-install) Nick
[O] Updating org from git repository
I have done this: cd ~/share/org-mode.git git checkout release_7.8.11 git checkout -b rel7.8.11 make make install I've already set up a ton of orgmode stuff in ~/.emacs, but Emacs was still finding the old org version. So I added: (add-to-list 'load-path "/home/dlm/share/org-mode.git/lisp") Now, when I reload orgmode, the minibuffer correctly shows "Org-mode version 7.8.11 (release_7.8.11 @ /home/dlm/share/org-mode.git/lisp/)" but... Export to PDF dies with: "org-version: Symbol's function definition is void: org-release" How do I complete the installation? hjh -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
On 17 July 2012 18:10, Rian Murphy wrote: > Christopher Witte witte.net.au> writes: > >> >> On 17 July 2012 16:53, Rian Murphy yahoo.com> wrote: >> > Giovanni Ridolfi yahoo.it> writes: >> > ... >> >> > I'd prefer to use capture on my Ubuntu installation. I searched the >> >> > gmane >> >> > archives and didn't find any clues. >> >> > ... >> >> Upgrading org is easy and there are instructions in the FAQ, >> http://orgmode.org/worg/org-faq.html#updating-org >> >> Chris. >> >> > Chris, thanks for your help. I should have looked in the org-mode > FAQ to start with -- I apologize. > Oddly, however, when I do a 'git pull' and a 'make up2', then restart > emacs, 'org-version' still tells me I have version 6.30c. > 'emacs-version' still says 23.1.50.1. > Maybe it's a Ubuntu thing Thanks again, R.M. > I don't think it's an Ubuntu thing, I keep up to date with the git repo under Ubuntu. Did you run 'make install'? You might need to run 'sudo make install'. You should also be able to refresh org without restarting emacs, I can't remember what the command is though.
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Christopher Witte witte.net.au> writes: > > On 17 July 2012 16:53, Rian Murphy yahoo.com> wrote: > > Giovanni Ridolfi yahoo.it> writes: > > ... > >> > I'd prefer to use capture on my Ubuntu installation. I searched the gmane > >> > archives and didn't find any clues. > >> ... > > Upgrading org is easy and there are instructions in the FAQ, > http://orgmode.org/worg/org-faq.html#updating-org > > Chris. > > Chris, thanks for your help. I should have looked in the org-mode FAQ to start with -- I apologize. Oddly, however, when I do a 'git pull' and a 'make up2', then restart emacs, 'org-version' still tells me I have version 6.30c. 'emacs-version' still says 23.1.50.1. Maybe it's a Ubuntu thing Thanks again, R.M.
Re: [O] Converting Org to Sweave (*.Rnw)
Julian Gehring writes:
> Hi,
>
> is there a way to convert Org-mode files with R code blocks to the
> Sweave ('*.Rnw') [1] file format or has anyone planned to work on
> this?
First, there is this thread:
http://comments.gmane.org/gmane.emacs.orgmode/7931
and then there is this
http://yihui.name/knitr/demo/org/
But I wanted more, and I think the new exporter provides some awesome
possibilities, so...
I have put together a rudimentary exporter for Sweave and for brew style
chunks and hope to have several of the knitr chunk flavors supported
soon. I've not looked closely, but I think pander can be supported, too.
The basic idea is to use the new export engine. See
http://orgmode.org/worg/dev/org-export-reference.html
for background.
The e-latex, e-html, and other modes are used as parent backends and
e-latex-rnw, e-html-brew, etc are *derived* backends. It is pretty easy
to hitch a ride on the work done to make a parent backend and then add a
minimal definition of the chunk formatting.
The only tricky bit is getting Babel to help in the process, but not
interfere. I want Babel to porcess non-R src blocks and clean out R
#+RESULTS blocks, but not strip out the header args, as these may be
wanted (as you suggest below) to inform the chunk arguments. I've
managed this by advise'ing org-babel-exp-do-export to do special
handling of R src blocks.
I've not yet delved into translating the headers into code chunk
arguments. Some like 'width' seem pretty obvious. Others like the
:exports + :results translation may take some thought. And there are
some idioms in Sweave and kntir that have not corresponding idiom in org
(which is a strong motive for doing this work) like 'dev' in knitr as
well as ':cache yes' versus 'cache=T', which are false cognates, so to
speak
So far, what I've done is do add a header arg like this:
Here is an inline chunk: src_R{ rnorm(1) } which the brew export
renders as <%= rnorm(1) -%> (i.e. print the result, but do not place
a line break after the result), making a non-printing version of this
is done by using this src_R[ :ravel <% -%> ]{ rnorm(1) }, which
renders as <% rnorm(1) -%>.
or this
: #+name: aCachedChunk
: #+begin_src R :ravel cache=T
: x <- rnorm(1e7)
: #+end_src
which is rendered as
<>=
x <- rnorm(1e7)
@ %def
when using the Sweave style exporters.
However, Nicolas *just* added support for #+ATTR_SOMETHING, where
SOMETHING is a user defined key. And I incline to the view that using
something like
: #+attr_ravel: cache=T
: #+name: aCachedChunk
: #+begin_src R
: x <- rnorm(1e7)
: #+end_src
might be preferred.
Anyway, I'll try to get a version up where you can have a look at it
sometime today.
I am keen to collaborate on this.
Chuck
>
> Sweave is heavily used in the R community in terms of literate
> programming, and has a tight integration into current package building
> workflows. Essentially, the file format is a latex document, with
> designated code chunks.
>
> Since Org/Org-babel offers a very similar feature set, and already
> covers the export to latex, I was wondering whether anyone is working
> on some code that would rewrite the code block headers in the export?
> In the R community, I have seen a lot of interest in such an exporter,
> that would allow to write the documentation in Org itself and later
> export it to several backends, including Sweave to integrate it in the
> R package.
>
> If anyone has some comments regarding this or is interested in working
> on this, please let me know. My colleagues and I would be very
> interested in contributing in projects in this direction.
>
>
> Best
> Julian
>
>
> [1] http://en.wikipedia.org/wiki/Sweave
>
>
>
--
Charles C. BerryDept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
On 17 July 2012 16:53, Rian Murphy wrote: > Giovanni Ridolfi yahoo.it> writes: > ... >> > I'd prefer to use capture on my Ubuntu installation. I searched the gmane >> > archives and didn't find any clues. >> >> Pelase, do >> M-x emacs-version >> and >> M-x org-version >> >> in both systems; then if version is < than 6.36, you should not have > capture, but only remember >> [[info:org#Capture]] >> > ... >> > Giovanni, > Thank you very much for your quick reply. > Sure enough, I had version 6.21b of org on my Ubuntu installation. > > Per your advice, I tried upgrading to Emacs 24. Apparently, 24 isn't > readily available for Ubuntu, but I got Damien Cassou's latest snapshot > following the instrucitons > in http://www.mikeyboldt.com/2011/11/30/install-emacs-24-in-ubuntu/. > It upgraded Emacs to 23.1.50.1 and org to 6.30c. > I guess I will have to live with 'remember' for a while. > > But thanks a lot for your help. R.M. > Upgrading org is easy and there are instructions in the FAQ, http://orgmode.org/worg/org-faq.html#updating-org Chris.
Re: [O] [new exporter] Bug: dates enclosed in angle brackets
Hello, Myles English writes: > A date entered with with C-c . exports without angle brackets in the old > exporter but with angle brackets in the new exporter. I would have > thought that without is preferable. Agreed. Brackets are only Org syntax. I have pushed a change about timestamp objects and planning elements. Regards, -- Nicolas Goaziou
[O] Remembrance Agent and Orgmode
Hi! In my research I stumbled upon Rememberance Agent[1][2] and since it does have a Debian package install candidate [3] I was thinking about giving it a try. This software (originally from MIT) seems to be quite handy and its features seems to be a perfect companion to Org-mode. There is also a nice video[4] where Thad Starner is using a headset and a "mobile" version of Emacs/RA. Be aware that this was 1996! It's a bit outdated (v2.12 2004-02-16) and after being installed on my Ubuntu, it makes the impression that much fiddling is needed to start indexing and stuff. Is there somebody still using RA? Is there some tutorial or how-to out there that helps a RA-newbie? Do you have lessons learned? Thanks! 1. http://www.remem.org/ 2. http://www.emacswiki.org/emacs/RemembranceAgents 3. http://packages.debian.org/de/sid/remembrance-agent 4. http://www.youtube.com/watch?v=k-zThJX920w -- Karl Voit
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Giovanni Ridolfi yahoo.it> writes: ... > > I'd prefer to use capture on my Ubuntu installation. I searched the gmane > > archives and didn't find any clues. > > Pelase, do > M-x emacs-version > and > M-x org-version > > in both systems; then if version is < than 6.36, you should not have capture, but only remember > [[info:org#Capture]] > ... > Giovanni, Thank you very much for your quick reply. Sure enough, I had version 6.21b of org on my Ubuntu installation. Per your advice, I tried upgrading to Emacs 24. Apparently, 24 isn't readily available for Ubuntu, but I got Damien Cassou's latest snapshot following the instrucitons in http://www.mikeyboldt.com/2011/11/30/install-emacs-24-in-ubuntu/. It upgraded Emacs to 23.1.50.1 and org to 6.30c. I guess I will have to live with 'remember' for a while. But thanks a lot for your help. R.M.
Re: [O] No inline property value after subtree export
Da: Miguel Ruiz
Inviato: Martedì 17 Luglio 2012 15:20
--org-mode file start
#+OPTIONS: toc:nil
#+AUTHOR:
#+DATE:
* Level 1
:PROPERTIES:
:ID: 527b694d-8288-4d37-a06a-a288bd9592b5
:END:
This is level 1 with ID {{{property(ID)}}}
** Level 2
:PROPERTIES:
:ID: 1cf7847a-0977-4f18-8dc1-c3058a89a596
:END:
This is level 2 with ID {{{property(ID)}}}
*** Level 3
:PROPERTIES:
:ID: 2b9390ca-17ea-452f-be68-28c134dd376e
:END:
This is level 3 with ID{{{property(ID)}}}
--org-mode file end ---
>if I do org-export then "1"(subtree) then "d"(LaTeX) with the cursor in the
>"Level 2"
> heading,
> I get "Level 2" as document title, but the ID value is not evaluated so I
> get {{{property(ID)}}} instead. The level 3 ID value is correctly exported.
I can confirm this bug Org-mode version 7.8.11 (69af0913b28d )
Also if I select C-c @ the first subtree (level 1) the ID value is not
evaluated for
Level 1 but it is evaluated for level 2 and 3.
The ID values are evaluated when exporting the entire document.
unfortunately I have not been able to export this file with the new exporter.
Giovanni
Re: [O] Org mode export to Groff MM. Feature Freeze
Nicolas Goaziou writes: Hi: > > An advantage of the new export engine is that a back-end can be as > simple as you want it to be. This is correct; you bring a good point. > One can imagine specialized back-ends only rendering a limited set of > Org features. As long as the set is explicitly documented in the > back-end, there's nothing wrong with that. Agreed. But, there's more to the story. I started dabbling with muse this morning at 4:00 AM (because that's the best time to play with emacs, just after the ghosts go to bed :) ). I got a fairly modest version running in muse that created a fairly believable man page. I realized some things during the experiment: 1. Although the subset of MAN macros is small for the creation of man pages, there are things that can be done procedurally during export that can enhance the look of the man page. The new Org backend makes this task a lot easier because of its flexibility and the availability of all data items through the "info" variable. The POD to man page does that, no reason why it cannot be done in Org. 2. The ability to render source code, or the execution of embedded code, would have a positive impact on the end result. I can work on a prototype on Org and see how it goes. -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Da: Rian Murphy Inviato: Martedì 17 Luglio 2012 15:32 Oggetto: [O] Emacs23 on Ubuntu recognizes 'remember', not 'capture' Hi, Rian > I am using emacs 23 on an Ubuntu server. I also use emacs 22 on a Macbook pro. > On the Macbook, I set up my .emacs file to use orgmode and defined several > capture templates. They work fine on the Macbook. > So I set up the .emacs file in the Ubuntu environment to start up org mode, > and > copied my capture templates over. When I tried to do a capture, however, emacs > (on Ubuntu) didn't recognize 'org-capture'. The only way I could get it to > work > is to change all the'capture' references in .emcas to 'remember', and > redo the templates using the remember syntax. > I'd prefer to use capture on my Ubuntu installation. I searched the gmane > archives and didn't find any clues. Pelase, do M-x emacs-version and M-x org-version in both systems; then if version is < than 6.36, you should not have capture, but only remember [[info:org#Capture]] > Would I have to somehow uninstall emacs 23 and install emacs 22? > Any other ideas? - Wouldn't be possible for you to Install emacs 24? - yopu can also try to download and install latest org (see org website) cheers, Giovanni
[O] Emacs23 on Ubuntu recognizes 'remember', not 'capture'
Hello, I am using emacs 23 on an Ubuntu server. I also use emacs 22 on a Macbook pro. On the Macbook, I set up my .emacs file to use orgmode and defined several capture templates. They work fine on the Macbook. So I set up the .emacs file in the Ubuntu environment to start up org mode, and copied my capture templates over. When I tried to do a capture, however, emacs (on Ubuntu) didn't recognize 'org-capture'. The only way I could get it to work is to change all the'capture' references in .emcas to 'remember', and redo the templates using the remember syntax. I'd prefer to use capture on my Ubuntu installation. I searched the gmane archives and didn't find any clues. Would I have to somehow uninstall emacs 23 and install emacs 22? Any other ideas? Thanks, R. Murphy
[O] No inline property value after subtree export
Hi,
In this minimal example
--org-mode file start#+OPTIONS:
toc:nil#+AUTHOR:#+DATE:* Level 1 :PROPERTIES: :ID:
527b694d-8288-4d37-a06a-a288bd9592b5 :END:This is level 1 with ID
{{{property(ID)}}}** Level 2 :PROPERTIES: :ID:
1cf7847a-0977-4f18-8dc1-c3058a89a596 :END:This is level 2 with ID
{{{property(ID)}}}*** Level 3 :PROPERTIES: :ID:
2b9390ca-17ea-452f-be68-28c134dd376e :END:This is level 3 with
ID{{{property(ID)}}}--org-mode file end ---
if I do org-export then "1"(subtree) then "d"(LaTeX) with the cursor in the
"Level 2" heading, I get "Level 2" as document title, but the ID value is not
evaluated so I get {{{property(ID)}}} instead. The level 3 ID value is
correctly exported.
Any hint to solve it?
Re: [O] A week off
On 07/16/2012 06:49 PM, Bastien wrote: Dear all, I'm taking a week off, with no internet connectivity. I'll be back online on July 24th. Mm, so does that mean we fill his inbox with packing peanuts or something? - Allen S. Rout
[O] Converting Org to Sweave (*.Rnw)
Hi,
is there a way to convert Org-mode files with R code blocks to the
Sweave ('*.Rnw') [1] file format or has anyone planned to work on this?
Sweave is heavily used in the R community in terms of literate
programming, and has a tight integration into current package building
workflows. Essentially, the file format is a latex document, with
designated code chunks.
Since Org/Org-babel offers a very similar feature set, and already
covers the export to latex, I was wondering whether anyone is working on
some code that would rewrite the code block headers in the export? In
the R community, I have seen a lot of interest in such an exporter, that
would allow to write the documentation in Org itself and later export it
to several backends, including Sweave to integrate it in the R package.
If anyone has some comments regarding this or is interested in working
on this, please let me know. My colleagues and I would be very
interested in contributing in projects in this direction.
Best
Julian
[1] http://en.wikipedia.org/wiki/Sweave
Re: [O] Org mode export to Groff MM. Feature Freeze
Hello, Luis Anaya writes: > It might be easier to implement a typesetter for MAN pages in muse mode > because it has a simpler rendering framework. It may also be a more > appropriate platform considering that MAN pages do not have a lot of > formatting requirements, when they are compared to a document > with multiple levels, lists, equations and graphics which is what you > find in papers, letters or memorandum. An advantage of the new export engine is that a back-end can be as simple as you want it to be. Sure, e-latex, e-odt, ... try to be as comprehensive as possible with regards to Org syntax, but it doesn't mean that every back-end has to handle every syntactic element. One can imagine specialized back-ends only rendering a limited set of Org features. As long as the set is explicitly documented in the back-end, there's nothing wrong with that. Note that I do not comment the comparison with Muse mode rendering framework, which I do not know. Regards, -- Nicolas Goaziou
Re: [O] [new exporter] fails on double backslashes
Hello, Thomas Holst writes: > right now I am testing the new exporter. It works very well except on > backslashes. Here is a minimal example which shows the problem: Indeed. It chokes on line break. It should be fixed now. Thank you for testing the new exporter and reporting this bug. Regards, -- Nicolas Goaziou
[O] [new exporter] Bug: dates enclosed in angle brackets
A date entered with with C-c . exports without angle brackets in the old exporter but with angle brackets in the new exporter. I would have thought that without is preferable. Thanks, Myles
[O] [new exporter] fails on double backslashes
Hello,
right now I am testing the new exporter. It works very well except on
backslashes. Here is a minimal example which shows the problem:
#+BEGIN_SRC org
#+TITLE: new-exporter.org
#+AUTHOR:Thomas Holst
#+EMAIL: thomas.ho...@de.bosch.com
#+DATE: 2012-07-16 Mo
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:{} -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:t todo:t pri:nil tags:t
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0
path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
* headline
some text \\
more text
#+END_SRC
When I try to export to LaTeX (M-x org-export-dispatch L) there is
an error:
and: Invalid search bound (wrong side of point)
No LaTeX code is produced.
This is with emacs -Q and only the relevant org files loaded:
emacs-vesion:
GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) of 2011-09-19 on 3249CTO
org-version:
Org-mode version 7.8.11
(release_7.8.11-196-g5dbd13 @
c:/daten/users/de_hts2fe/git/org-mode/lisp/)
OS: WinXP (also tested with emacs 23.2)
I know that it does not make sense to have an empty line after the
backslashes, but I think there should be no error. It only happens when
there is an empty line after the backslashes. Without the empty line
there is no error.
Backtrace:
Debugger entered--Lisp error: (error "Invalid search bound (wrong side of
point)")
re-search-forward("[^]\\(\\)[ ]*$" 518 t)
(and (re-search-forward "[^]\\(\\)[ ]*$" limit t)
(goto-char (match-beginning 1)))
(let ((beg (and (re-search-forward "[^]\\(\\)[]*$" limit t)
(goto-char (match-beginning 1) (when (and beg (re-search-backward "\\S-"
(point-at-bol) t)) (cons (quote line-break) beg)))
(save-excursion (let ((beg (and (re-search-forward "[^]\\(\\)[
]*$" limit t) (goto-char (match-beginning 1) (when (and beg
(re-search-backward "\\S-" (point-at-bol) t)) (cons (quote line-break) beg
org-element-line-break-successor(518)
funcall(org-element-line-break-successor 518)
(let* ((successor-fun (intern (format "org-element-%s-successor" (or (cdr
(assq type org-element-object-successor-alist)) type (obj (funcall
successor-fun limit))) (and obj (push obj next-candidates)))
(lambda (type) (let* ((successor-fun (intern (format
"org-element-%s-successor" (or (cdr ...) type (obj (funcall successor-fun
limit))) (and obj (push obj next-candidates(line-break)
mapc((lambda (type) (let* ((successor-fun (intern (format
"org-element-%s-successor" (or (cdr ...) type (obj (funcall successor-fun
limit))) (and obj (push obj next-candidates (line-break))
(let (next-candidates types-to-search) (if (not objects) (setq
types-to-search restriction) (mapc (lambda (obj) (if (< (cdr obj) (point))
(push (car obj) types-to-search) (push obj next-candidates))) objects)) (mapc
(lambda (type) (let* ((successor-fun (intern (format "org-element-%s-successor"
...))) (obj (funcall successor-fun limit))) (and obj (push obj
next-candidates types-to-search) next-candidates)
org-element-get-next-object-candidates(518 (export-snippet footnote-reference
inline-babel-call inline-src-block latex-or-entity line-break link macro
radio-target statistics-cookie sub/superscript target text-markup timestamp)
((line-break . 516)))
(setq candidates (org-element-get-next-object-candidates end restriction
candidates))
(while (setq candidates (org-element-get-next-object-candidates end
restriction candidates)) (let ((next-object (let ((pos (apply ... ...)))
(save-excursion (goto-char pos) (funcall (intern ...)) (let ((obj-beg
(org-element-property :begin next-object))) (unless (= (point) obj-beg) (setq
acc (org-element-adopt-element acc (replace-regexp-in-string " " (make-string
tab-width 32) (buffer-substring-no-properties ... obj-beg)) t (let
((obj-end (org-element-property :end next-object)) (cont-beg
(org-element-property :contents-begin next-object))) (when (and (memq (car
next-object) org-element-recursive-objects) cont-beg) (save-restriction
(narrow-to-region cont-beg (org-element-property :contents-end next-object))
(org-element-parse-objects (point-min) (point-max) next-object
(org-element-restriction next-object (setq acc (org-element-adopt-element
acc next-object t)) (goto-char obj-end
(save-excursion (goto-char beg) (while (setq candidates
(org-element-get-next-object-candidates end restriction candidates)) (let
((next-object (let ((pos ...)) (save-excursion (goto-char pos) (funcall
...) (let ((obj-beg (org-element-property :begin next-object))) (unless (=
(point) obj-beg) (setq acc (org-element-adopt-element acc
(replace-regexp-in-string "" ... ...) t (let ((obj-end
(org-element-property :end next-object)) (cont-beg (org-element-property
:contents-
Re: [O] Org mode export to Groff MM. Feature Freeze
Nicolas Goaziou writes:
> You just have to put
>
> (add-to-list 'org-element-block-name-alist
>'("GROFF" . org-element-export-block-parser))
>
> in org-e-groff.el so BEGIN_GROFF/END_GROFF blocks are treated as export
> blocks again. No need to remove anything in your text pre-processing
> because of this.
This looks vaguely familiar :( I think this was the change I made in
org-export.el. Let me add that on the org-e-groff.el code.
Thanks for your help.
--
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Org mode export to Groff MM. Feature Freeze
Hello,
Luis Anaya writes:
>- The change with the largest imapct on my code had to do with
> the BEGIN_GROFF/END_GROFF pairs in which now invokes the special
> block function and process the enclosed text through the plain-text
> function. Originally these were passed through without the
> invocation of the plain text function.
>
> I had to remove all the text pre-processing being that it was causing
> problems in the execution of GROFF macros. I do not think that
> doing this will hurt (much) because of the GROFF markup syntax.
> For instance:
>
> TeX/LaTeX looks like this:
> \begin{center}
> Blah
> \end
> while GROFF looks like this.
> .DS C
> Blah
> .DE
>
> French quotations are not supported now because of this change, quotes are
> significant in GROFF for many things and I cannot translate those
> because GROFF will fail with a syntax error.
You just have to put
(add-to-list 'org-element-block-name-alist
'("GROFF" . org-element-export-block-parser))
in org-e-groff.el so BEGIN_GROFF/END_GROFF blocks are treated as export
blocks again. No need to remove anything in your text pre-processing
because of this.
Regards,
--
Nicolas Goaziou
