Re: [Orgmode] Re: Bibtex and latex export
On Thu, 07 Oct 2010 16:11:32 -0400, Nick Dokos wrote: > > Eric S Fraga wrote: > > > > echo /foo | egrep '^(/|[A-z]:/)' > > > > > > do you get the bad range end error message? If so, then your egrep > > > is indeed stricter than mine. > > > > I do indeed: > > > > : egrep: Invalid range end. > > > > Very strange. > > > > > > > LC_ALL=C texi2dvi ... > > > > > > > > but this may have unexpected side effects? I'm not sure if any of the > > > > latex suite use the locale... > > > > > > Yeah, perhaps... > > > > Interestingly, it *is* a locale issue: > > > > : $ echo /foo | LC_ALL=C egrep '^(/|[A-z]:/)' > > : /foo > > > > Yup: the egrep man page says > > , > | Within a bracket expression, a range expression consists of two > | characters separated by a hyphen. It matches any single character that > | sorts between the two characters, inclusive, using the locale’s > | collating sequence and character set. For example, in the default C > | locale, [a-d] is equivalent to [abcd]. Many locales sort characters in > | dictionary order, and in these locales [a-d] is typically not equivalent > | to [abcd]; it might be equivalent to [aBbCcDd], for example. To obtain > | the traditional interpretation of bracket expressions, you can use the C > | locale by setting the LC_ALL environment variable to the value C. > ` > > So as Achim pointed out, unless texi2dvi explicitly specifies the locale > for egrep, that regexp is busted. Even [A-Za-z] is busted in the absence > of a locale: it would have to be something like [:alpha:], although I'm > not sure what DOS allows/requires as a drive prefix. And even in the C > locale, [A-z] allows non-letters which, I'm pretty sure, cannot be used > as drive prefixes. > > Nick > Okay, I think this has convinced me to file a bug report. I'll start with Debian's system (reporting a bug against the texinfo package) and hope it filters upstream appropriately. texi2dvi definitely does not specify the locale for egrep. [:alpha:] is probably the right choice from the little I know about DOS... -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [BUG] define "just", preamble and postamble placement
Łukasz Stelmach wrote: > |---+-| > | Preamble| > |---+-| > | | | > | Content | TOC | > | | | > |---+-| > | Postamble | > |---+-| > > I'd like to have a layout like the above one, with (pre|post)ambles of > full width (or at least as wide a the content + TOC). With the present > layout preamble and postamble are siblings to TOC and the text and I > can't get the desired layout. > I guess it depends on what you start with and how much you are willing to do by hand (or by extra programming). Are you trying to get this layout by html-exporting an org file without any massaging of the resulting HTML/CSS? If so, I don't know how to do it - I don't know if it's even possible with just the stock org-mode html export mechanism: org has certain conventions about the HMTL it produces and although it is possible to bend them (e.g. Sebastian Rose's org-info.js magic transformation of standard HTML into info-like docs or folded outlines - who'd have thunk it?), afaik it requires some surgery (e.g. in addition to Sebaastian's JS script, one needs some machinery on the org-mode side: org-jsinfo.el, that is very much tailored to Sebastian's script and a line in the org file to get the whole thing moving). If you are willing to write some CSS, I think it's quite possible to get the layout you want (but you may need to add e.g. ids to various elements in the HTML - I haven't looked at the HTML that org produces in any detail to see what it puts in and what it leaves out). In particular, I don't think that the parent/sibling structure of the DOM tree limits you in any way as far as the layout goes: the just gives you a different containing block element; if it wasn't there, the element would be the containing block element - but does that really make much difference? And if the preamble/postamble were outside the div, the tree structure would be different but so what? Minor adjustments in the CSS would take care of it, I should think. But as I said, I'm no expert and I may very well be mistaken. Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] How can I just publish entry marked as DONE?
I am using org project to build my web page. I have written a lot of stuff but while I am publishing the org files, I just want to publish the part which are marked as DONE( the keyword ). Is it possbile? Thanks Water Lin -- The Big Bang on Busy Reading: http://bigbang.WaterLin.org Email: water...@sohu.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Any equal setting of #+STARTUP: nologdone?
I am using following setting --- #+STARTUP: nologdone --- to avoid done log note while I mark one entry as DONE. But I want to set it as a global setting to avoid use it for every org file. Is there any equal setting of #+STARTUP: nologdone while I am setting my project using following code: (setq org-publish-project-alist ? Thanks Water Lin -- The Big Bang on Busy Reading: http://bigbang.WaterLin.org Email: water...@sohu.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
On 7 October 2010 06:58, Eric S Fraga wrote:
> On Thu, 07 Oct 2010 09:29:59 -0400, Nick Dokos wrote:
>>
>> Eric S Fraga wrote:
>>
>> > On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz wrote:
>> > >
>> > > Hi Eric,
>> > >
>> > > Eric S Fraga writes:
>> > > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
>> > > > | egrep: Invalid range end
>> > > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex,
>> > > > skipping.
>> > >
>> > > Something somewhere tries to make a local path from an absolute one by
>> > > prepending "./", which fails (predictably). Is the input readable at
>> > > the original path? Not sure the error message from egrep has to do with
>> > > it or not, but it must be in any case one of the processes started by
>> > > texi2dvi (does not show up on my system, I only have calls to grep when
>> > > I trace it, but one of the sub-processes might still use it). I think
>> > > texi2dvi also invokes shell scripts, so any funny configuration in the
>> > > environment, especially where path points to, could throw it off.
>> >
>> > As far as I know, there is nothing out of the ordinary with my paths
>> > etc (please note that the /.../ above was an edit on my part to hide a
>> > rather long path). Any hints as to what I can do to explore this
>> > would be most helpful. How can I get a trace on what texi2dvi is
>> > doing? (sh -v /usr/bin/texi2dvi?)
>> >
>>
>> There is an explicit egrep on line 1563 or thereabouts (my version
>> says
>>
>> # texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
>> # $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $
>>
>> at the top of the file):
>>
>>
>> # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
>> # prepend `./' in order to avoid that the tools take it as an option.
>> echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
>> || command_line_filename="./$command_line_filename"
>>
>>
>> The regular expression seems a bit weird (upper case A to lower case
>> z?), but I can't see off the top of my head how it gets tripped up. For
>> tracing, try
>>
>> sh -x texi2dvi
>>
>> Nick
>
> Thanks Nick. If I do this:
>
> : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
>
> the following is a snippet of the output:
>
> ,
> | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep ^(/|[A-z]:/)
> | egrep: Invalid range end
> | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
> | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex,
> skipping.
> `
>
> Because the egrep fails completely, the script assumes that it does
> need to prepend "./" to the file name even though the file name
> already starts with "/" (and is definitely *not* a DOS type file name
> ;-).
>
> I don't understand why the egrep is failing although it definitely has
> something to do with A-z range; if I try the egrep at the shell and
> use "A-Za-z" instead of "A-z", the command works fine. Does it work
> for anybody else on Linux?
>
> I wonder if the problem with the range is locale dependent? My locale
> is en_GB.UTF-8. The manual page for egrep does indicate that ranges
> may not mean the same thing in different locales and suggests using
> locale C. I don't want to change my locale but maybe it could be set
> for the invocation of texi2dvi... (yech).
>
> This is obviously not an org problem as such but I am surprised it's
> working for anybody at all...
>
> I guess I'll stick to multiple invocations of pdflatex directly for
> the time being.
>
I have the exact same problem ever since I updated org today. (from
commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
Eric Schulte)
My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
understand the discussion where the bug actually is. To resolve this
do I need to file a bug with the Fedora bugzilla? I am confused how
can that be possible because I can successfully export to pdf if I
downgrade org to commit 344785b.
Any suggestions welcome.
> cheers,
> eric
>
--
Suvayu
Open source is the future. It sets us free.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] entities and removing some markup in ascii export
I was trying to get rid of some markup (or get it properly "translated")
when exporting to ascii/latin1/utf8.
For example:
ORG-BLOCKQUOTE-START
I have nothing to say and I am Saying it.
ORG-BLOCKQUOTE-END
could be exported as:
I have nothing to say and I am Saying it.
Regarding LaTeX markup I'd like to get delimiters like "$", "$$", "\(",
"\)", "\[", and "\]" removed. Other markup such as "\mathit", "\mathrm",
etc. should be treated as if using italics and normal text respectively.
"\frac{n}{m}" sohuld be translated as "n/m" and so on...
As i am writing this I discovered org-entities-ascii-explanatory and
org-entities-user. I'll try to customize them.
Also, in a previous posting I asked about conditional export, this could
be another (worse) way to solve the problem. ¿Should I use emacs-lisp
SRC blocks? ¿Could anyone provide an example, please?
Thank you
--
Ezequiel Birman
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Option to prevent auto-insertion of blank lines by M-return?
Sorry if this is an obvious question, but I'm not having much luck finding the right org-mode customization options (due to the fact that there are so many of them, in combination with my relative noobness). Here's the behavior I would like to change: I have outline headings with a blank line in between, e.g. *** MIDI class 2 <2010-10-14 Thu 08:45> *** MIDI class 3 <2010-10-21 Thu 08:45> And I want to add more headings underneath MIDI class 2. So I put the cursor at the end of the "MIDI class 2" line and hit M-return. Then I get this: *** MIDI class 2 <2010-10-14 Thu 08:45> *** *** MIDI class 3 <2010-10-21 Thu 08:45> But I would rather get this: *** MIDI class 2 <2010-10-14 Thu 08:45> *** *** MIDI class 3 <2010-10-21 Thu 08:45> I sort of understand that it's replicating the blank space between headings, but I would rather put in the blank space if I want it, instead of the tool assuming that I want it and then forcing me to take it out. Hoping for a customize option... thanks! James -- 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 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Option to prevent auto-insertion of blank lines by M-return?
Hi James, this is a FAQ: http://orgmode.org/worg/org-faq.php#blank-line-after-headlines-and-list-items - Carsten On Oct 8, 2010, at 11:29 AM, James Harkins wrote: Sorry if this is an obvious question, but I'm not having much luck finding the right org-mode customization options (due to the fact that there are so many of them, in combination with my relative noobness). Here's the behavior I would like to change: I have outline headings with a blank line in between, e.g. *** MIDI class 2 <2010-10-14 Thu 08:45> *** MIDI class 3 <2010-10-21 Thu 08:45> And I want to add more headings underneath MIDI class 2. So I put the cursor at the end of the "MIDI class 2" line and hit M-return. Then I get this: *** MIDI class 2 <2010-10-14 Thu 08:45> *** *** MIDI class 3 <2010-10-21 Thu 08:45> But I would rather get this: *** MIDI class 2 <2010-10-14 Thu 08:45> *** *** MIDI class 3 <2010-10-21 Thu 08:45> I sort of understand that it's replicating the blank space between headings, but I would rather put in the blank space if I want it, instead of the tool assuming that I want it and then forcing me to take it out. Hoping for a customize option... thanks! James -- 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 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Option to prevent auto-insertion of blank lines by M-return?
Perfect! Thanks. In case anyone is searching list archives... the answer is: org-blank-before-new-entry. James PS Org-mode is *saving my bacon* on a big multimedia composition project due for performance in about 2 weeks. I might have been able to keep track of the details with something else, but the human-readable file format of org-mode is a winner for me. So thanks for the very excellent work on a deep, pleasant-to-use tool! On Fri, Oct 8, 2010 at 5:35 PM, Carsten Dominik wrote: > Hi James, > > this is a FAQ: > > > http://orgmode.org/worg/org-faq.php#blank-line-after-headlines-and-list-items > > - Carsten > > > On Oct 8, 2010, at 11:29 AM, James Harkins wrote: > > Sorry if this is an obvious question, but I'm not having much luck finding >> the right org-mode customization options (due to the fact that there are so >> many of them, in combination with my relative noobness). >> >> Here's the behavior I would like to change: I have outline headings with a >> blank line in between, e.g. >> >> *** MIDI class 2 <2010-10-14 Thu 08:45> >> >> *** MIDI class 3 <2010-10-21 Thu 08:45> >> >> And I want to add more headings underneath MIDI class 2. So I put the >> cursor at the end of the "MIDI class 2" line and hit M-return. Then I get >> this: >> >> *** MIDI class 2 <2010-10-14 Thu 08:45> >> >> *** >> >> *** MIDI class 3 <2010-10-21 Thu 08:45> >> >> But I would rather get this: >> >> *** MIDI class 2 <2010-10-14 Thu 08:45> >> *** >> >> *** MIDI class 3 <2010-10-21 Thu 08:45> >> >> I sort of understand that it's replicating the blank space between >> headings, but I would rather put in the blank space if I want it, instead of >> the tool assuming that I want it and then forcing me to take it out. >> >> Hoping for a customize option... thanks! >> James >> >> >> -- >> 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 >> ___ >> Emacs-orgmode mailing list >> Please use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> > > - Carsten > > > > -- 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 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Version string (was Re: ELPA Howto)
On Oct 5, 2010, at 1:09 PM, Jambunathan K wrote: In the context of ELPA packages, I think there might be a need to revisit how orgmode's version string is defined. For example, 7.01h wouldn't be successfully parsed by (version-to-list ...) which the package manager uses internally. So 7.01h could be mapped to 7.0.1.8 or 7.1.8. Hi Jambunthan, in what places would the version string have to be modified? Do I need to change the org.el variable org-version, or the string in the VERSION keyword in file headers, or where? - Carsten ,[ C-h f version-to-list RET ] | version-to-list is a compiled Lisp function in `subr.el'. | | (version-to-list VER) | | Convert version string VER into an integer list. | | The version syntax is given by the following EBNF: | |VERSION ::= NUMBER ( SEPARATOR NUMBER )*. | |NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+. | |SEPARATOR ::= `version-separator' (which see) | | `version-regexp-alist' (which see). | | The NUMBER part is optional if SEPARATOR is a match for an element | in `version-regexp-alist'. | | As an example of valid version syntax: | |1.0pre2 1.0.7.5 22.8beta3 0.9alpha1 6.9.30Beta | | As an example of invalid version syntax: | |1.0prepre2 1.0..7.5 22.8X3 alpha3.2 .5 | | As an example of version convertion: | |String VersionInteger List Version |"1.0.7.5" (1 0 7 5) |"1.0pre2" (1 0 -1 2) |"1.0PRE2" (1 0 -1 2) |"22.8beta3" (22 8 -2 3) |"22.8Beta3" (22 8 -2 3) |"0.9alpha1" (0 9 -3 1) |"0.9AlphA1" (0 9 -3 1) |"0.9alpha"(0 9 -3) | | See documentation for `version-separator' and `version-regexp- alist'. | | [back] ` Jambunathan K. - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Header levels and section numbering > 3, in LaTeX export
I couldn't get easylist to understand the
\star symbol that orgmode uses. Do you know how to do that?
No. You might have seen the footnote in the easylist documentation
(on p. 2) which says:
"You might not be happy with the symbols and maybe you'd like to use
another one, or simply have your favorite symbol
as default to avoid remembering such a cumbersome name as 'pilcrow'.
Here's a simple hack that does the job: select the
entire code of the package, and replace all occurrences of Ÿ (<<-- the
pilcrow) with your symbol. Make sure you won't use it in the list for
other purposes, though."
I've not tried this, however. It would be nice if there were a dead
easy way to get easylist and org-mode to work well together, since the
two are very natural partners. Let me know if you can make this work.
I couldn't get either \star nor \ast to work so I'm just using \sharp
now, and am simply replacing # (at beginning of the line) with a hook.
I'm not sure which is the best hook to use though. I don't want to alter
my orgmode buffer and also want the hook to run on orgmode syntax. So
far, I've failed at this.
org-export-first-hook runs in my orgmode buffer and alters the contents.
org-export-latex-after-blockquotes-hook runs after latex export has
already happened (ie \section etc have already been converted)
Maybe there's a hook in the middle somewhere, but I couldn't find any
documentation on it.
And also to skip
the first 3 stars in a level4 heading (if I want to retain latex's default
top 3 levels)?
I've never actually gone all the way to making a document
easy-to-publish with Easylist. I've just manually converted
org-mode's stars to a character Easylist can understand, then manually
wrapped the whole thing in a LaTeX preamble. The ideal would be to
automate the process, perhaps by using org-babel and putting your
easylist sections in special code blocks. But I've not taken the time
to figure all that out.
I do not even know what babel is, although I've heard it in a ton of
different contexts. Considering what the word "babel" means, I'm not
even sure if that is strange or not!
Failing that, I bet you could do a halfway hack with minimal amount of
manual work. For example (if I understand you correctly), you could
make an org document like this:
* Regular org heading
** Subheading
** Here's a third-level heading
STARTLIST
My first thesis, which is longer and wordier than it probably should be.
* Of course it's nothing compared to the length of its supporting arguments
* Both of them
Here is my second thesis, as convincing as the first
ENDLIST
Org-mode will let you do all of that, just fine. Then either
manually, or with a temporary latex export hook, do something like
this:
replace STARTLIST with \begin{easylist} and ENDLIST with \end{easylist}
replace ' ' with '& ' and '* ' with'&& ' and ** ' with'&&& ',
etc.
If you do it in an export hook, I think you'd want to do it in one
that runs before everything else. That way org-mode will leave
everthing in your easylist environment alone. What that will do to
quotation marks and /emphasis/ I don't know.
This is exactly what I want to do, but which export hook to use?
Something that will not modify my original buffer and also understand
regexp that I can base on what was originally in my buffer. So instead
of searching for \paragraph, I can search for " ", but I want to
keep " " in my original org buffer.
Indraneel
This should leave you with an easylist which starts at level '1', in a
document which uses org's header levels 1-3 in the normal latex way.
Is that what you want?
Make sure in the preamble, you have \usepackage[ampersand]{easylist}
Let me know if you need help figuring any of this out in detail.
That's just a rough sketch.
Cheers,
Scot
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Feature idea: overwrite time at the prompt when rescheduling
I use rescheduling often and it would be convenient if I didn't have to delete the existing time at the schedule prompt and I could just type the new time (like 8am) which would automatically replace (overwrite) the previous text in the prompt. Sometimes it is also useful to edit the existing time at the prompt, so it could work by checking what is the first thing I do after invoking reschedule. If I start typing immediately it should delete the previous contents of the prompt, but if I do anything else (cursor movement, deletion) then it should let me edit the current contents. Also a special highlight could indicate that the existing contents will be overwritten with typing. Like it is customary in GUI programs, when the text in the input field is selected then typing overwrites it. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] library of babel, bootabs question
I'm trying to export a document to LaTeX, using a lob-call to booktabs for a table. Unfortunately I seem to get two tables, the original one and the one from the lob call. The table looks like this: #+tblname: ma |---+---+-| | row 1 cell 1 header | row 1 cell 2 header | r1c3 header | | row 2 cell 1 header | row 2 cell 2 header | r2c3 header | |---+---+-| | some text inside tabl | some text, some text | more text | | more text | more text | more text | | more text | more text | more text | |---+---+-| #+call: booktabs(table=ma, align="lll") :results latex :exports results Did I forget some option? I didn't find any in the manuals. Thanks a lot for any help. Robert ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
On Fri, 8 Oct 2010 01:43:25 -0700, suvayu ali
wrote:
[...]
>
> I have the exact same problem ever since I updated org today. (from
> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
> Eric Schulte)
>
> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
> understand the discussion where the bug actually is. To resolve this
> do I need to file a bug with the Fedora bugzilla? I am confused how
> can that be possible because I can successfully export to pdf if I
> downgrade org to commit 344785b.
>
> Any suggestions welcome.
>
> > cheers,
> > eric
> >
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
Suvayu,
the bug is due to the expression in the texi2dvi script used in an
egrep command. The reason it is hitting you now and not before is
that the default sequence of commands for exporting org files to PDF
has changed from a sequence of "pdflatex" and "bibtex" commands to one
of using only "texi2dvi". You can fix the problem by changing the
variable org-latex-to-pdf-process. I have set it to
: ("pdflatex %f" "bibtex %f" "pdflatex %f" "pdflatex %f")
and this works just fine for me. If you don't need bibtex at all, you
can remove that entry. You only need multiple runs of pdflatex if you
have cross-references (including tables of contents etc).
This is a solution in one sense but the real bug is the egrep
expression in texi2dvi which is why it is suggested that a bug report
be filed.
HTH,
eric
--
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Version string (was Re: ELPA Howto)
Hi, so how do we move forward with generating packages? I have installed the code by Jambunthan in the Make file, but I guess we still need to negotiate with the EPLA on how to upload and update the package, about name conventions etc. Is there anyone whole is willing to sort this all out and then show us the simple upload recipe? My feeling is that the latest release should be on the package server. daily bleeding edge builds could be there as well, under a different name. Thanks - Carsten On Oct 8, 2010, at 12:38 PM, Carsten Dominik wrote: On Oct 5, 2010, at 1:09 PM, Jambunathan K wrote: In the context of ELPA packages, I think there might be a need to revisit how orgmode's version string is defined. For example, 7.01h wouldn't be successfully parsed by (version-to- list ...) which the package manager uses internally. So 7.01h could be mapped to 7.0.1.8 or 7.1.8. Hi Jambunthan, in what places would the version string have to be modified? Do I need to change the org.el variable org-version, or the string in the VERSION keyword in file headers, or where? - Carsten ,[ C-h f version-to-list RET ] | version-to-list is a compiled Lisp function in `subr.el'. | | (version-to-list VER) | | Convert version string VER into an integer list. | | The version syntax is given by the following EBNF: | |VERSION ::= NUMBER ( SEPARATOR NUMBER )*. | |NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+. | |SEPARATOR ::= `version-separator' (which see) | | `version-regexp-alist' (which see). | | The NUMBER part is optional if SEPARATOR is a match for an element | in `version-regexp-alist'. | | As an example of valid version syntax: | |1.0pre2 1.0.7.5 22.8beta3 0.9alpha1 6.9.30Beta | | As an example of invalid version syntax: | |1.0prepre2 1.0..7.5 22.8X3 alpha3.2 .5 | | As an example of version convertion: | |String VersionInteger List Version |"1.0.7.5" (1 0 7 5) |"1.0pre2" (1 0 -1 2) |"1.0PRE2" (1 0 -1 2) |"22.8beta3" (22 8 -2 3) |"22.8Beta3" (22 8 -2 3) |"0.9alpha1" (0 9 -3 1) |"0.9AlphA1" (0 9 -3 1) |"0.9alpha"(0 9 -3) | | See documentation for `version-separator' and `version-regexp- alist'. | | [back] ` Jambunathan K. - Carsten - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bibtex and latex export
suvayu ali writes:
> On 7 October 2010 06:58, Eric S Fraga wrote:
>> On Thu, 07 Oct 2010 09:29:59 -0400, Nick Dokos wrote:
>>>
>>> Eric S Fraga wrote:
>>>
>>> > On Wed, 06 Oct 2010 19:21:33 +0200, Achim Gratz wrote:
>>> > >
>>> > > Hi Eric,
>>> > >
>>> > > Eric S Fraga writes:
>>> > > > | /usr/bin/texi2dvi: Processing /home/ucecesf/.../file.tex ...
>>> > > > | egrep: Invalid range end
>>> > > > | /usr/bin/texi2dvi: cannot read .//home/ucecesf/.../file.tex,
>>> > > > skipping.
>>> > >
>>> > > Something somewhere tries to make a local path from an absolute one by
>>> > > prepending "./", which fails (predictably). Is the input readable at
>>> > > the original path? Not sure the error message from egrep has to do with
>>> > > it or not, but it must be in any case one of the processes started by
>>> > > texi2dvi (does not show up on my system, I only have calls to grep when
>>> > > I trace it, but one of the sub-processes might still use it). I think
>>> > > texi2dvi also invokes shell scripts, so any funny configuration in the
>>> > > environment, especially where path points to, could throw it off.
>>> >
>>> > As far as I know, there is nothing out of the ordinary with my paths
>>> > etc (please note that the /.../ above was an edit on my part to hide a
>>> > rather long path). Any hints as to what I can do to explore this
>>> > would be most helpful. How can I get a trace on what texi2dvi is
>>> > doing? (sh -v /usr/bin/texi2dvi?)
>>> >
>>>
>>> There is an explicit egrep on line 1563 or thereabouts (my version
>>> says
>>>
>>> # texi2dvi --- produce DVI (or PDF) files from Texinfo (or (La)TeX) sources.
>>> # $Id: texi2dvi,v 1.104 2007/09/10 00:36:30 karl Exp $
>>>
>>> at the top of the file):
>>>
>>>
>>> # If the COMMAND_LINE_FILENAME is not absolute (e.g., --debug.tex),
>>> # prepend `./' in order to avoid that the tools take it as an option.
>>> echo "$command_line_filename" | $EGREP '^(/|[A-z]:/)' >&6 \
>>> || command_line_filename="./$command_line_filename"
>>>
>>>
>>> The regular expression seems a bit weird (upper case A to lower case
>>> z?), but I can't see off the top of my head how it gets tripped up. For
>>> tracing, try
>>>
>>> sh -x texi2dvi
>>>
>>> Nick
>>
>> Thanks Nick. If I do this:
>>
>> : (setq org-latex-to-pdf-process '("sh -x /usr/bin/texi2dvi -p -b -c -V %f"))
>>
>> the following is a snippet of the output:
>>
>> ,
>> | + echo /home/ucecesf/s/teaching/cape/lectures/matlab.tex+ egrep
>> ^(/|[A-z]:/)
>> | egrep: Invalid range end
>> | + command_line_filename=.//home/ucecesf/s/teaching/cape/lectures/matlab.tex
>> | + test -r .//home/ucecesf/s/teaching/cape/lectures/matlab.tex
>> | + error 1 cannot read .//home/ucecesf/s/teaching/cape/lectures/matlab.tex,
>> skipping.
>> `
>>
>> Because the egrep fails completely, the script assumes that it does
>> need to prepend "./" to the file name even though the file name
>> already starts with "/" (and is definitely *not* a DOS type file name
>> ;-).
>>
>> I don't understand why the egrep is failing although it definitely has
>> something to do with A-z range; if I try the egrep at the shell and
>> use "A-Za-z" instead of "A-z", the command works fine. Does it work
>> for anybody else on Linux?
>>
>> I wonder if the problem with the range is locale dependent? My locale
>> is en_GB.UTF-8. The manual page for egrep does indicate that ranges
>> may not mean the same thing in different locales and suggests using
>> locale C. I don't want to change my locale but maybe it could be set
>> for the invocation of texi2dvi... (yech).
>>
>> This is obviously not an org problem as such but I am surprised it's
>> working for anybody at all...
>>
>> I guess I'll stick to multiple invocations of pdflatex directly for
>> the time being.
>>
>
> I have the exact same problem ever since I updated org today. (from
> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06
> Eric Schulte)
>
> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite
> understand the discussion where the bug actually is. To resolve this
> do I need to file a bug with the Fedora bugzilla? I am confused how
> can that be possible because I can successfully export to pdf if I
> downgrade org to commit 344785b.
Hi suvayu ali,
The change probably is in commit
59ba412 (Use texi2dvi for processing LaTeX to pdf, 2010-10-05)
where we switch from using pdflatex to texi2dvi if it is available.
Regards,
Bernt
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [babel] Writing R-packages the org way?
Hi Chuck,
I agree about making use of existing ESS tools and that a more
traditional Org approach might be appropriate.
> If you do decide to go all in for a 'one org file makes one package'
> approach, you might try to get Rd language support added, so you can
> edit Rd directly in an Org Src buffer in Rd-mode.
No extra code is needed to get editing support for languages.
#+begin_src XXX
provides an edit buffer in XXX-mode automatically, with no special
customization. Also fontification in the org buffer works automatically
if `org-src-fontify-natively' is set.
Dan
> And get
> org-babel-Rd-evaluate to run Rd-preview-help or call Rd2HTML or
> whatnot.
>
> HTH,
>
> Chuck
>
>> Then, to insert a template, you can use
>>
>> #+call: R-pkg-template(function_name="do.something") :results output org raw
>>
>> which should give something like this:
>>
>> --8<---cut here---start->8---
>> #+results: R-pkg-template(function_name="do.something")
>> * do.something
>> ** Help
>> *** Title
>>this is do.something title
>> *** Description
>>do.something does this...
>> *** Usage
>>do.something(arg1, arg2, ...)
>> *** Arguments
>>arg1: the first argument
>> *** Examples
>>do.something(arg1 = x, arg2 = y)
>> ** Definition
>>begin_src R :tangle R/package.R
>>do.something <- function(arg1, arg2) {
>>
>>}
>> --8<---cut here---end--->8---
>>
>> While playing about you may want to get rid of the "raw" directive so
>> that the results will automatically be replaced on repeated evaluations.
>>
>> Dan
>>
>>>
>>>
>>>
>> Any suggestions how to best proceed?
>>>
>>> Dream: I would like to have one org file which contains everything
>>> (documentation, code, other relevant files) and if I export or
>>> tangle the file, I have the package ready.
>>>
>> Well, that functionality is essentially present with code blocks
>> and tangling, except the documentation part.
>>
>
>>> Exactly - and that is the part I would like to have.
>>>
>>>
> Hi Erik,
>
> Would you mind expanding on that -- what are we missing for the
> documentation part?
>
>
Dan, by "except for the documentation part", I meant generating
.Rd files (the LaTeX-like syntax) automatically from some org-syntax
that does *not* depend on code blocks. I.e., it would be cool to
specify syntax like I have above for documentation. Using org-mode
headlines for each section like Description, Usage, Arguments, etc.
Just like exporting to LaTeX generates sections, some process would
use these headlines to generate the .Rd sections.
That way, you don't have to use the .Rd syntax yourself. No big deal,
just a convenience feature. I don't know how you'd specify to org-mode
that a particular subtree was to generate .Rd syntax, and I don't know
if it would be on export or tangling.
An alternative is simply just to use code blocks of type Rd within
org-mode and then tangle to .Rd files. That's what I currently do.
Hope that explains it,
Erik
Dan
>
>>
>> ___
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
> Charles C. Berry(858) 534-2098
> Dept of Family/Preventive Medicine
> E mailto:cbe...@tajo.ucsd.edu UC San Diego
> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>
>
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Orgmode meetup at FOSDEM, February 2011. Who would come?
Richard Moreland writes: > On Mon, Oct 4, 2010 at 4:38 AM, Carsten Dominik > wrote: >> Still we need someone who says "I will organize this". >> Who will do that? > > If no one else volunteers, I will. We are getting close to the deadline for the application for a dev room. I will be on holiday and off-line for a week tomorrow, so I do not have time to work on this next week. I would love for this to happen, so the question is if I have to do this tonight (when the kids are in bed and I should do the packing, my wife is going to love this :-)), next Saturday or if I can rely on you to do this application. Also when doing the application I would open up the dev room to Emacs hackers in general, i.e. when mentioning the participating projects simply add Gnu Emacs. I'm sure if we offer a venue there are some Emacs hackers that are willing to come and participate. This will hopefully increase our chances of getting a room. So in essence I would change the application as follows: * Devroom name Org-mode and Emacs hackers * Devroom description ** Topics Org-mode is for keeping notes, maintaining ToDo lists, doing project planning, and authoring with a fast and effective plain-text system. Org-mode is based on GNU Emacs, an extensible, customizable text editor. *** Org-mode The Org-mode devroom will include a collection of talks from its author as well as speakers representing various other components of Org-mode. Developers will discuss the direction of Org-mode, identify additional tools that would be useful to surround Org-mode, as well as make a plan for widening its audience and making it more accessible to new users. *** Emacs development Emacs development has seen a renewed interest in the last years. There is a lot of activity in the developer community. Therefore this devroom will not only host many fine Org-mode Emacs Lisp hackers but is also open for other Emacs Lisp related subjects around developing with or for Emacs. *** Proposed Talks Some of our proposed talks include: - Org-babel a system for Literate Programming - GTD with Org-mode - Scientific applications - Sharing Org-mode data with other applications (TaskJuggler, ..?) - Org-mode on the iPhone, Android and Nokia devices - Managing websites with Org-mode (jekyll integration, built-in publishing, etc) - Power user demonstrations/tip sharing - The future of Org-mode ** Goals - Expose new and existing Org-mode users to demonstrations/application of features they might not have otherwise discovered - Identify new applications of Org-mode, help users get started using/customizing Org-mode for their domain - Collect members from the Org-mode mailing list in a single place for the first time - Share and refine the direction of Org-mode - Identify how contributors can help with Org-mode development/documentation/etc. - Plan for making Org-mode easier to get started with ** Target Projects - Org-mode - Emacs development * Devroom related URLs - http://orgmode.org - http://orgmode.org/worg/ - http://orgmode.org/worg/org-contrib/babel/index.php - http://orgmode.org/worg/org-tutorials/org-screencasts/index.php - http://mobileorg.ncogni.to/ - http://www.gnu.org/software/emacs/ - http://blog.gmane.org/gmane.emacs.devel * Name of the responsible - Richard Moreland - Christian Egli * Email - r...@ncogni.to - christian.e...@sbs.ch * Relation to the topic What ever you fancy, e.g - community manager - developer * Remarks Org-mode is a good match for FOSDEM since it brings together a diverse community across many platforms (Unix, Windows, Mac, Mobile) and fosters a renaissance of text-only power tools. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Orgmode meetup at FOSDEM, February 2011. Who would come?
On Fri, Oct 8, 2010 at 8:25 AM, Christian Egli wrote: > Richard Moreland writes: >> If no one else volunteers, I will. > > We are getting close to the deadline for the application for a dev room. > I will be on holiday and off-line for a week tomorrow, so I do not have > time to work on this next week. I would love for this to happen, so the > question is if I have to do this tonight (when the kids are in bed and I > should do the packing, my wife is going to love this :-)), next Saturday > or if I can rely on you to do this application. > Thanks Christian. I agree with your changes, and I have no problem following through with the application submission. If anyone has changes to make or suggestions for improving upon the updated proposal, please follow up soon. I'd like to get it submitted sooner than later in case there is any type of 'first come first served' weighting. If no one objects, I'll submit it on 10/10. -Richard ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Any equal setting of #+STARTUP: nologdone?
On Fri, Oct 08, 2010 at 04:39:26PM +0800, Water Lin wrote: > I am using following setting > --- > #+STARTUP: nologdone > --- > to avoid done log note while I mark one entry as DONE. > > But I want to set it as a global setting to avoid use it for every org > file. Hi Water, The customizable variable 'org-log-done' is the global setting for all files. Change it via M-x customize-variable, or by including "(setq org-log-done nil)" in your .emacs. Documentation for org-log-done: Information to record when a task moves to the DONE state. Possible values are: nil Don't add anything, just change the keyword timeAdd a time stamp to the task notePrompt for a note and add it with template `org-log-note-headings' > Is there any equal setting of #+STARTUP: nologdone while I am setting my > project using following code: > > (setq org-publish-project-alist > > ? I'm lost here. I can't see the relation between TODO state logging and project publishing. Regards, .j. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [babel] Writing R-packages the org way?
Dan Davison writes: > Hi Chuck, > > I agree about making use of existing ESS tools and that a more > traditional Org approach might be appropriate. this may be slightly off-topic, but another way of adding documentation is to the 'roxygen' markup. http://roxygen.org/ ESS has some support for editing roxygen comment chunks within ESS buffers, Stephen ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] how to reverse a region of outline items
hi all! I have a region of outline items with subitems like - A * text below A * ... - B * text below B - C - D * text below D ... - E - .. I want to reverse the list to: - .. - E - D * text below D ... - C - B * text below B - A * text below A * ... without loosing the connection to the subitems, therefore the "reverse-region" command will not work. Has anybody an idea? Rainer ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] bug with respect to org-read-date-prefer-future
Hi, Recently, but I cannot say for how long, I have found that dates entered, for instance using "j" in the standard agenda view, no longer choose a time/day in the future but seem to default to the current year. For instance, today, typing "j 2 feb RET" (with a real space between 2 and feb) jumps me to 2010 February 2, not 2011. #+begin_src emacs-lisp :results (describe-variable 'org-read-date-prefer-future) #+end_src #+results: #+begin_example org-read-date-prefer-future is a variable defined in `org.el'. Its value is time Documentation: Non-nil means assume future for incomplete date input from user. This affects the following situations: 1. The user gives a month but not a year. For example, if it is April and you enter "feb 2", this will be read as Feb 2, *next* year. "May 5", however, will be this year. 2. The user gives a day, but no month. For example, if today is the 15th, and you enter "3", Org-mode will read this as the third of *next* month. However, if you enter "17", it will be considered as *this* month. If you set this variable to the symbol `time', then also the following will work: 3. If the user gives a time, but no day. If the time is before now, to will be interpreted as tomorrow. Currently none of this works for ISO week specifications. When this option is nil, the current day, month and year will always be used as defaults. You can customize this variable. #+end_example so according to the documentation should work as I expect but doesn't... Have I misunderstood something? Thanks, eric #+begin_src emacs-lisp :results (format "%s\n%s\n" (org-version) (emacs-version)) #+end_src #+results: : Org-mode version 7.01trans (release_7.01h.645.g09015) : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) : of 2010-08-14 on raven, modified by Debian -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [BUG] MobileOrg blocked tasks showing up on agendas
I'm not quite sure if this is intended or not, but take this example. Say I have * Parent Project :PROPERTIES: :ORDERED: t :END: ** TODO task 1 ** TODO task 2 and I have org-enforce-todo-dependencies set to t and org-agenda-dim-blocked-tasks set to 'invisible When I do a a push and pull it down on my iPhone, task 2 is showing up in my agenda. Should it be hiding it? Luke ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [babel] Writing R-packages the org way?
On Fri, Oct 8, 2010 at 2:10 PM, Dan Davison wrote:
> Hi Chuck,
>
> I agree about making use of existing ESS tools and that a more
> traditional Org approach might be appropriate.
>
OK. But I think I have a solution for the "One package in a single org file"
approach - see below
>
> > If you do decide to go all in for a 'one org file makes one package'
> > approach, you might try to get Rd language support added, so you can
> > edit Rd directly in an Org Src buffer in Rd-mode.
>
> No extra code is needed to get editing support for languages.
> #+begin_src XXX
>
> provides an edit buffer in XXX-mode automatically, with no special
> customization. Also fontification in the org buffer works automatically
> if `org-src-fontify-natively' is set.
>
Agreed - and that is the key to it.
If one is using the post-tangle-hook to compile / check the package, the
fuinctiona;ity is together:
Example, the name of the org file will be used as the packagename:
BEGIN---
* Internal configurations
:noexport:
** Post tangle script
#+begin_src sh :tangle postTangleScript.sh :var PACKAGENAME=(or
(buffer-file-name) org-current-export-file)
R CMD CHECK $PACKAGENAME
#+end_src
** Evaluate to run post tangle script
#+begin_src emacs-lisp :results silent :tangle no :exports none
(add-hook 'org-babel-post-tangle-hook
(
lambda ()
(call-process-shell-command "./postTangleScript.sh" nil
0 nil)
)
)
#+end_src
* Package description
#+begin_src :tangle ./PACKAGENAME/DESCRIPTION
#+end_src
* Content of the package
** Function1
*** man
#+begin_src Rd :tangle ./PACKAGENAME/man/Function1.Rd
#+end_src
*** Code
#+begin_src R :tangle ./PACKAGENAME/R/Function1.R
#+end_src
*** Tests
#+begin_src R :tangle ./PACKAGENAME/tests/Function1Tests.R
#+end_src
The output from the test needs to be saved in
./PACKAGENAME/tests/Function1Tests.R - I still have to think about that.
** Function2
*** man
#+begin_src Rd :tangle ./PACKAGENAME/man/Function2.Rd
#+end_src
*** Code
#+begin_src R :tangle ./PACKAGENAME/R/Function2.R
#+end_src
*** Tests
#+begin_src R :tangle ./PACKAGENAME/tests/Function2Tests.R
#+end_src
The output from the test needs to be saved in
./PACKAGENAME/tests/Function2Tests.R - I still have to think about that.
** data
#+begin_src ...
#+end_src
This depends on the type of the data.
END---
This is untested so far, but I will try it out. The only thing which would
be nice, would be to automate a few things.
Cheers,
Rainer
>
> Dan
>
> > And get
> > org-babel-Rd-evaluate to run Rd-preview-help or call Rd2HTML or
> > whatnot.
> >
> > HTH,
> >
> > Chuck
> >
> >> Then, to insert a template, you can use
> >>
> >> #+call: R-pkg-template(function_name="do.something") :results output org
> raw
> >>
> >> which should give something like this:
> >>
> >> --8<---cut here---start->8---
> >> #+results: R-pkg-template(function_name="do.something")
> >> * do.something
> >> ** Help
> >> *** Title
> >>this is do.something title
> >> *** Description
> >>do.something does this...
> >> *** Usage
> >>do.something(arg1, arg2, ...)
> >> *** Arguments
> >>arg1: the first argument
> >> *** Examples
> >>do.something(arg1 = x, arg2 = y)
> >> ** Definition
> >>begin_src R :tangle R/package.R
> >>do.something <- function(arg1, arg2) {
> >>
> >>}
> >> --8<---cut here---end--->8---
> >>
> >> While playing about you may want to get rid of the "raw" directive so
> >> that the results will automatically be replaced on repeated evaluations.
> >>
> >> Dan
> >>
> >>>
> >>>
> >>>
>
> >> Any suggestions how to best proceed?
> >>>
> >>> Dream: I would like to have one org file which contains everything
> >>> (documentation, code, other relevant files) and if I export or
> >>> tangle the file, I have the package ready.
> >>>
> >> Well, that functionality is essentially present with code blocks
> >> and tangling, except the documentation part.
> >>
> >
> >>> Exactly - and that is the part I would like to have.
> >>>
> >>>
>
> > Hi Erik,
> >
> > Would you mind expanding on that -- what are we missing for the
> > documentation part?
> >
> >
> Dan, by "except for the documentation part", I meant generating
> .Rd files (the LaTeX-like syntax) automatically from some org-syntax
> that does *not* depend on code blocks. I.e., it would be cool to
> specify syntax like I have above for documentation. Using org-mode
> headlines for each section like Description, Usage, Arguments, etc.
>
> Just like exporting to LaTeX generates sections, some process would
> use these headlines to generate the .Rd sections.
>
> That way, you don't have to use the .Rd syntax yourself. No big deal,
> just a convenience fe
[Orgmode] Re: Version string (was Re: ELPA Howto)
(Resent to mailing-list) Carsten Dominik writes: > On Oct 5, 2010, at 1:09 PM, Jambunathan K wrote: > >> >> In the context of ELPA packages, I think there might be a need to >> revisit how orgmode's version string is defined. >> >> For example, 7.01h wouldn't be successfully parsed by (version-to-list >> ...) which the package manager uses internally. >> >> So 7.01h could be mapped to 7.0.1.8 or 7.1.8. > > > Hi Jambunthan, > > in what places would the version string have to be modified? > Do I need to change the org.el variable org-version, or the string in > the VERSION keyword in file headers, or where? > >From a functional perspective, there is *no need* to modify any of the el files. One has to just take care that PKG_TAG is a 'version-to-list'-compatible string. The tarball thus generated will be very much usable. >From a maintenance perspective you might want to move away from 7.01h convention and adopt a convention that is dictated by elpa. Jambunathan K. > - Carsten > >> >> ,[ C-h f version-to-list RET ] >> | version-to-list is a compiled Lisp function in `subr.el'. >> | >> | (version-to-list VER) >> | >> | Convert version string VER into an integer list. >> | >> | The version syntax is given by the following EBNF: >> | >> |VERSION ::= NUMBER ( SEPARATOR NUMBER )*. >> | >> |NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+. >> | >> |SEPARATOR ::= `version-separator' (which see) >> | | `version-regexp-alist' (which see). >> | >> | The NUMBER part is optional if SEPARATOR is a match for an element >> | in `version-regexp-alist'. >> | >> | As an example of valid version syntax: >> | >> |1.0pre2 1.0.7.5 22.8beta3 0.9alpha1 6.9.30Beta >> | >> | As an example of invalid version syntax: >> | >> |1.0prepre2 1.0..7.5 22.8X3 alpha3.2 .5 >> | >> | As an example of version convertion: >> | >> |String VersionInteger List Version >> |"1.0.7.5" (1 0 7 5) >> |"1.0pre2" (1 0 -1 2) >> |"1.0PRE2" (1 0 -1 2) >> |"22.8beta3" (22 8 -2 3) >> |"22.8Beta3" (22 8 -2 3) >> |"0.9alpha1" (0 9 -3 1) >> |"0.9AlphA1" (0 9 -3 1) >> |"0.9alpha"(0 9 -3) >> | >> | See documentation for `version-separator' and `version-regexp- >> alist'. >> | >> | [back] >> ` >> >> Jambunathan K. > > - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
On 8 October 2010 04:35, Eric S Fraga wrote:
> On Fri, 8 Oct 2010 01:43:25 -0700, suvayu ali
> wrote:
>
> [...]
> Suvayu,
>
> the bug is due to the expression in the texi2dvi script used in an
> egrep command. The reason it is hitting you now and not before is
> that the default sequence of commands for exporting org files to PDF
> has changed from a sequence of "pdflatex" and "bibtex" commands to one
> of using only "texi2dvi". You can fix the problem by changing the
> variable org-latex-to-pdf-process. I have set it to
>
> : ("pdflatex %f" "bibtex %f" "pdflatex %f" "pdflatex %f")
>
> and this works just fine for me. If you don't need bibtex at all, you
> can remove that entry. You only need multiple runs of pdflatex if you
> have cross-references (including tables of contents etc).
>
> This is a solution in one sense but the real bug is the egrep
> expression in texi2dvi which is why it is suggested that a bug report
> be filed.
>
Hi Eric,
Thanks a lot for the explanation and the fix for now. I'll definitely
file a bug report with Fedora.
> HTH,
> eric
>
> --
> Eric S Fraga
> GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
>
>
--
Suvayu
Open source is the future. It sets us free.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bibtex and latex export
Hi Bernt, On 8 October 2010 05:01, Bernt Hansen wrote: > suvayu ali writes: > >> >> >> I have the exact same problem ever since I updated org today. (from >> commit 344785b 2010-10-03 Bernt Hansen to commit 0901585 2010-10-06 >> Eric Schulte) >> >> My locale is en_IN.utf8, and I am on Fedora 13. I couldn't quite >> understand the discussion where the bug actually is. To resolve this >> do I need to file a bug with the Fedora bugzilla? I am confused how >> can that be possible because I can successfully export to pdf if I >> downgrade org to commit 344785b. > > Hi suvayu ali, > > The change probably is in commit > 59ba412 (Use texi2dvi for processing LaTeX to pdf, 2010-10-05) > where we switch from using pdflatex to texi2dvi if it is available. > Thank you! I found the lines that changed the behaviour for me. :) > Regards, > Bernt > -- Suvayu Open source is the future. It sets us free. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [babel] Writing R-packages the org way?
On Fri, Oct 8, 2010 at 3:09 PM, Stephen Eglen wrote: > > > > Dan Davison writes: > > > Hi Chuck, > > > > I agree about making use of existing ESS tools and that a more > > traditional Org approach might be appropriate. > > this may be slightly off-topic, but another way of adding documentation > is to the 'roxygen' markup. > http://roxygen.org/ Actually not - I did not specify that I want to use .Rd . > > ESS has some support for editing roxygen comment chunks within ESS > buffers, > Yes - I looked into Roxygen some time ago, but in the context of org, I see it as not necessary to include the documentation in the source code block - when using #+begin_src Rd #+end_src and #+begin_src R #+end_src I can nicely separate these two on the code level - but in the org file, they are still literate programming. Cheers, Rainer > Stephen > > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > -- NEW GERMAN FAX NUMBER!!! Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Cell: +27 - (0)83 9479 042 Fax:+27 - (0)86 516 2782 Fax:+49 - (0)321 2125 2244 email: rai...@krugs.de Skype: RMkrug Google: r.m.k...@gmail.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] library of babel, bootabs question
Hi Robert, Currently the only way I know of inhibiting the export of the original table, is to move it to an un-exporting subtree. This can be done using the COMMENT header keyword by moving the table to a new subtree and pressing C-c ; which runs org-toggle-comment in that subtree. Best -- Eric "Robert Klein" writes: > I'm trying to export a document to LaTeX, using a lob-call to booktabs > for a table. > > Unfortunately I seem to get two tables, the original one and the one > from the lob call. > > The table looks like this: > > > #+tblname: ma > |---+---+-| > | row 1 cell 1 header | row 1 cell 2 header | r1c3 header | > | row 2 cell 1 header | row 2 cell 2 header | r2c3 header | > |---+---+-| > | some text inside tabl | some text, some text | more text | > | more text | more text | more text | > | more text | more text | more text | > |---+---+-| > #+call: booktabs(table=ma, align="lll") :results latex :exports results > > > Did I forget some option? I didn't find any in the manuals. > > > Thanks a lot for any help. > Robert > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
Eric S Fraga wrote: > This is a solution in one sense but the real bug is the egrep > expression in texi2dvi which is why it is suggested that a bug report > be filed. > texi2dvi includes the following address for bug reports: bug-texi...@gnu.org so maybe *one* of the people filing a bug report with debian/fedora/etc should cc: this address. Eric, do you want to do that? FWIW, I just tried echo /foo | egrep '^(/|[A-z]:/)' on Ubuntu 10.04 and egrep does not complain. Can you guys try egrep -V and see what version of egrep you are running? On Ubuntu 8.10: egrep -V says GNU grep 2.5.3 On Ubuntu 10.04: egrep -V says GNU grep 2.5.4 and neither of these is picky about the regexp. Thanks, Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
Hi Nick, On 8 October 2010 08:51, Nick Dokos wrote: > Eric S Fraga wrote: > >> This is a solution in one sense but the real bug is the egrep >> expression in texi2dvi which is why it is suggested that a bug report >> be filed. >> > > texi2dvi includes the following address for bug reports: > > bug-texi...@gnu.org > > so maybe *one* of the people filing a bug report with debian/fedora/etc > should cc: this address. Eric, do you want to do that? > > FWIW, I just tried > > echo /foo | egrep '^(/|[A-z]:/)' > > on Ubuntu 10.04 and egrep does not complain. I get "egrep: Invalid range end" on Fedora 13 and works as expected on Ubuntu 10.04 (pdf export works as expected here). > Can you guys try > > egrep -V > > and see what version of egrep you are running? > > On Ubuntu 8.10: egrep -V says GNU grep 2.5.3 > On Ubuntu 10.04: egrep -V says GNU grep 2.5.4 > > and neither of these is picky about the regexp. > For me, GNU grep 2.6.3 on Fedora 13 (fails) GNU grep 2.5.4 on Ubuntu 10.04 (works) > Thanks, > Nick > > -- Suvayu Open source is the future. It sets us free. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
There is a thread in the bugs-texinfo mailing list on the egrep problem in texi2dvi: http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bibtex and latex export
I'm pretty sure that this behaviour of egrep has been introduced with GNU grep version 2.6 (which says it fixed some long-standing bugs with regards to locale handling and character classes if you care to read the release notes). Unfortunately, as we see here, fixing bugs in one place often uncovers bugs someplace else, as the texi2dvi maintainers certainly didn't suspect a new version of grep to cause breakage. There are some bugs introduced with 2.6 that supposedly have been fixed in 2.7. Since the intent of the regex is obviously to allow an absolute path to start either with a "/" or a DOS drive letter, contrary to what I wrote before it is _not_ possible to use character classes as that would also allow extra characters not allowed in drive letters in most locales. Probably the most compatible version is to force the "C" locale for the egrep call in question and slightly modify the range expression: echo "$command_line_filename" | LC_ALL=C $EGREP '^(/|[A-Za-z]:/)' >&6 \ || command_line_filename="./$command_line_filename" Otherwise you can't really use range expressions or character classes at all since they either permit illegal drive letters or might not work with due to the bugs in older versions of grep... it would however be possible to spell out each drive letter bot in upper and lower case, although that handicaps the permissible length of the filename (if the "-i" switch wasn't broken in some locales one could use it and save one version of the cases): echo "$command_line_filename" | LC_ALL=C $EGREP \ '^(/|[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz]:/)' >&6 \ || command_line_filename="./$command_line_filename" *Shudder* :-) Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bibtex and latex export
Nick Dokos writes: > There is a thread in the bugs-texinfo mailing list on the egrep > problem in texi2dvi: > > http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html They came to the same conclusion... :-) Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
On Fri, 08 Oct 2010 13:27:15 -0400, Nick Dokos wrote: > > There is a thread in the bugs-texinfo mailing list on the egrep > problem in texi2dvi: > > http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html > > Nick > Yeah, it sure looks like we're not the only runs bitten by this bug. I guess there's no point in filing a bug with them but I may still do it with Debian. Thanks for digging this up. The scary thing is that nobody seems to be seriously suggesting fixing this on that list? Also, nobody has suggested [:alpha:] as a replacement, although this may not be strictly correct for DOS disk designators if alpha includes all accented letters etc... -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bibtex and latex export
Achim Gratz wrote: > Otherwise you can't really use range expressions or character classes at > all since they either permit illegal drive letters or might not work > with due to the bugs in older versions of grep... it would however be > possible to spell out each drive letter bot in upper and lower case, > although that handicaps the permissible length of the filename (if the > "-i" switch wasn't broken in some locales one could use it and save one > version of the cases): > > echo "$command_line_filename" | LC_ALL=C $EGREP \ > '^(/|[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz]:/)' >&6 \ > || command_line_filename="./$command_line_filename" > > *Shudder* :-) > Indeed :-) There is a locale-independent range spec for regexps: [:alpha:] would match the indicated class in any locale. See the egrep man page for more of these. I sent some mail to bug-texi...@gnu.org suggesting this, so we'll see. I also found out to my surprise from the previously posted bug-texinfo thread, that the ASCII characters between 'Z' and 'a' are (or were) legal drive letters, but the assumption is that nobody would be so foolish as to use them any more, so not checking for them is OK. Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp
FYI: Karl Berry's reply - afaict, it does not solve everything ( the regexp might mean different things in different locales), but is it good enough for its limited purpose (detecting drive letters)? Nick --- Forwarded Message Date:Fri, 08 Oct 2010 18:38:00 + From:k...@freefriends.org (Karl Berry) To: nicholas.do...@hp.com cc: bug-texi...@gnu.org Subject: Re: Nick Dokos: texi2dvi egrep regexp texi2dvi: locale-dependent error in egrep [A-z] (see http://lists.gnu.org/archive/html/bug-texinfo/2010-03/msg00031.html and following). Has anything come of that? Yes, I already changed it at that time to [A-Za-z]. However, of course that was in the development sources, so people using the latest (= old) release aren't going to be helped. texi2dvi is a standalone script so people with problems could conceivably download it and use it themselves. Not that I'd especially recommend that as a widespread practice, of course. I don't know when the next full release will be. karl --- End of Forwarded Message ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: bug with respect to org-read-date-prefer-future
Eric S Fraga writes: > Recently, but I cannot say for how long, I have found that dates > entered, for instance using "j" in the standard agenda view, no longer > choose a time/day in the future but seem to default to the current > year. For instance, today, typing "j 2 feb RET" (with a real space > between 2 and feb) jumps me to 2010 February 2, not 2011. > > > #+begin_src emacs-lisp :results > (describe-variable 'org-read-date-prefer-future) > #+end_src > > #+results: > #+begin_example > org-read-date-prefer-future is a variable defined in `org.el'. > Its value is time > > Documentation: > Non-nil means assume future for incomplete date input from user. > This affects the following situations: > 1. The user gives a month but not a year. > For example, if it is April and you enter "feb 2", this will be read > as Feb 2, *next* year. "May 5", however, will be this year. > 2. The user gives a day, but no month. > For example, if today is the 15th, and you enter "3", Org-mode will > read this as the third of *next* month. However, if you enter "17", > it will be considered as *this* month. > > If you set this variable to the symbol `time', then also the following > will work: > > 3. If the user gives a time, but no day. If the time is before now, > to will be interpreted as tomorrow. > > Currently none of this works for ISO week specifications. > > When this option is nil, the current day, month and year will always be > used as defaults. > > You can customize this variable. > #+end_example > > so according to the documentation should work as I expect but > doesn't... Have I misunderstood something? > > Thanks, > eric > > > #+begin_src emacs-lisp :results > (format "%s\n%s\n" (org-version) (emacs-version)) > #+end_src > > #+results: > : Org-mode version 7.01trans (release_7.01h.645.g09015) > : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) > : of 2010-08-14 on raven, modified by Debian Hi Eric, This was recently changed in commit 03b178d (Do not prefer future when jumping to a date in the agenda, 2010-09-21) by Carsten after an offline discussion with me. The behaviour changed for the 'j' command in the agenda only but not for other date prompts. The justification for this was at the start of a new month you need to enter the year to go back to a date a week or two ago in the agenda which seemed inconvenient. Carsten noticed that I had set org-read-date-prefer-future to nil in http://doc.norang.ca/org-mode.html and questioned why that was necessary. After a short discussion he decided to change the default behaviour for the agenda j command only. Please comment on whether this change is good or bad. The docstring should be more clear about this change if we decide to keep it. Regards, Bernt ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bibtex and latex export
Nick Dokos writes: > I also found out to my surprise from the previously posted bug-texinfo > thread, that the ASCII characters between 'Z' and 'a' are (or were) legal > drive letters, but the assumption is that nobody would be so foolish as > to use them any more, so not checking for them is OK. Ah yes, the LASTDRIVE=32 hack (Novell, I think?). That's pretty theoretical since most applications couldn't use them anyway, but that didn't stop MS from later copying it. It sure doesn't work if you try and shove these through a POSIX command line... BTW, Wikipedia has a good writeup on that, much to my surprise: http://en.wikipedia.org/wiki/Drive_letter_assignment Ob-org (enough off-topic for today): once we get the lettered lists, we should have a LASTDRIVE configuration option to allow [\]^_` as additional list members when lists get longer than 26 elements... ;-P Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: bug with respect to org-read-date-prefer-future
Bernt Hansen writes: > The justification for this was at the start of a new month you need to > enter the year to go back to a date a week or two ago in the agenda > which seemed inconvenient. Fair enough, but at the end of the year you certainly wouldn't expect to jump back almost a year by the same reasoning, so intead of having a choice to "prefer future" or "keep strictly the same year/month/day" unconditionally one should be able to say how much of the past should be considered. Not unlike how most spreadsheet programs today allow you to configure what range of years should be used if you enter just two digits. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: bug with respect to org-read-date-prefer-future
On Fri, 08 Oct 2010 15:01:49 -0400, Bernt Hansen wrote: > > Eric S Fraga writes: > > > Recently, but I cannot say for how long, I have found that dates > > entered, for instance using "j" in the standard agenda view, no longer > > choose a time/day in the future but seem to default to the current > > year. For instance, today, typing "j 2 feb RET" (with a real space > > between 2 and feb) jumps me to 2010 February 2, not 2011. [...] > > Hi Eric, > > This was recently changed in commit > 03b178d (Do not prefer future when jumping to a date in the agenda, > 2010-09-21) > by Carsten after an offline discussion with me. > > The behaviour changed for the 'j' command in the agenda only but not for > other date prompts. Ah, okay, so I am not totally losing it... ;-) > The justification for this was at the start of a new month you need to > enter the year to go back to a date a week or two ago in the agenda > which seemed inconvenient. > > Carsten noticed that I had set org-read-date-prefer-future to nil in > http://doc.norang.ca/org-mode.html and questioned why that was > necessary. After a short discussion he decided to change the default > behaviour for the agenda j command only. > > Please comment on whether this change is good or bad. The docstring > should be more clear about this change if we decide to keep it. > > Regards, > Bernt Well, I must say that I prefer the old way as it is more likely (on a simple probabilistic view considering the full twelve months of the year) that I am going to want a future date if I refer to a month before the current one. I can understand your justification for earlier in a month but I typically simply use, say, -7 or -10 then (as I use +7 or +10 say for days in the future). So, I guess my view is that the change is more bad than good... At the very least, I would like this to be configurable, if that is at all possible? If not, I am sure I can adjust! By the way, I guess I could see an argument for a date alone being for the current month, whether future or past, much as time can be considered already to be for the current day, whether future or past, if the variable is configured as I have it (time), but even then we should have a configurable variable? Regardless, the docs definitely have to change! Thanks, eric -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: bug with respect to org-read-date-prefer-future
Eric S Fraga writes: > On Fri, 08 Oct 2010 15:01:49 -0400, Bernt Hansen wrote: >> >> Eric S Fraga writes: >> >> > Recently, but I cannot say for how long, I have found that dates >> > entered, for instance using "j" in the standard agenda view, no longer >> > choose a time/day in the future but seem to default to the current >> > year. For instance, today, typing "j 2 feb RET" (with a real space >> > between 2 and feb) jumps me to 2010 February 2, not 2011. > > [...] > >> >> Hi Eric, >> >> This was recently changed in commit >> 03b178d (Do not prefer future when jumping to a date in the agenda, >> 2010-09-21) >> by Carsten after an offline discussion with me. >> >> The behaviour changed for the 'j' command in the agenda only but not for >> other date prompts. > > Ah, okay, so I am not totally losing it... ;-) > >> The justification for this was at the start of a new month you need to >> enter the year to go back to a date a week or two ago in the agenda >> which seemed inconvenient. >> >> Carsten noticed that I had set org-read-date-prefer-future to nil in >> http://doc.norang.ca/org-mode.html and questioned why that was >> necessary. After a short discussion he decided to change the default >> behaviour for the agenda j command only. >> >> Please comment on whether this change is good or bad. The docstring >> should be more clear about this change if we decide to keep it. >> >> Regards, >> Bernt > > Well, I must say that I prefer the old way as it is more likely (on a > simple probabilistic view considering the full twelve months of the > year) that I am going to want a future date if I refer to a month > before the current one. I can understand your justification for > earlier in a month but I typically simply use, say, -7 or -10 then (as > I use +7 or +10 say for days in the future). So, I guess my view is > that the change is more bad than good... At the very least, I would > like this to be configurable, if that is at all possible? If not, I > am sure I can adjust! > > By the way, I guess I could see an argument for a date alone being for > the current month, whether future or past, much as time can be > considered already to be for the current day, whether future or past, > if the variable is configured as I have it (time), but even then we > should have a configurable variable? > > Regardless, the docs definitely have to change! Personally I'm okay with reverting this commit if it is problematic. I'll leave the final decision on that up to Carsten. -Bernt ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Any equal setting of #+STARTUP: nologdone?
Juan Pechiar writes: > On Fri, Oct 08, 2010 at 04:39:26PM +0800, Water Lin wrote: >> I am using following setting >> --- >> #+STARTUP: nologdone >> --- >> to avoid done log note while I mark one entry as DONE. >> >> But I want to set it as a global setting to avoid use it for every org >> file. > > Hi Water, > > The customizable variable 'org-log-done' is the global setting for all > files. Change it via M-x customize-variable, or by including "(setq > org-log-done nil)" in your .emacs. > > Documentation for org-log-done: > > Information to record when a task moves to the DONE state. > > Possible values are: > > nil Don't add anything, just change the keyword > timeAdd a time stamp to the task > notePrompt for a note and add it with template > `org-log-note-headings' Thank, I got it. Water Lin > >> Is there any equal setting of #+STARTUP: nologdone while I am setting my >> project using following code: >> >> (setq org-publish-project-alist >> >> ? > > I'm lost here. I can't see the relation between TODO state logging and > project publishing. > > Regards, > .j. > -- The Big Bang on Busy Reading: http://bigbang.WaterLin.org Email: water...@sohu.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] TaskJuggler 3, revisited
Hi, I'm coming up on some serious need for a project manager. I really only need gantt chart creation at this point. I strongly dislike the Qt interface and the need to use that if one wants to get a gantt chart output from the process. I would much prefer being able to design my html charts, print them as PDFs or take screenshots and embed them in presentations, send them to others, etc. (as per tj3). - is there any progress on an exporter for tj3? - does anyone have a vague sketch of what needs to happen? - can I do grunt work for someone to make this happen? --- scan files for particular variables? --- run test code, put together all the errors, and send back? --- something else? I'm happy to help... I just don't have the programming skills to do the "real work" that needs to happen. Thanks for any input, John ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp
Hi everyone, On 8 October 2010 11:51, Nick Dokos wrote: > FYI: Karl Berry's reply - afaict, it does not solve everything ( the > regexp might mean different things in different locales), but is it > good enough for its limited purpose (detecting drive letters)? > I have filed a bug report on the Fedora bugzilla[1] pointing to all the relevant discussions about this issue. Feel free to add to/edit it. Thanks everyone for narrowing this down. :) > Nick > [1] https://bugzilla.redhat.com/show_bug.cgi?id=641534 -- Suvayu Open source is the future. It sets us free. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Version string (was Re: ELPA Howto)
Attaching the response from Chong Yidong to my queries. Read down below. Jambunathan K. Carsten Dominik writes: > Hi, > > so how do we move forward with generating packages? I have installed > the code by Jambunthan in the Make file, but I guess we still need to > negotiate with the EPLA on how to upload and update the package, about > name conventions etc. > > Is there anyone whole is willing to sort this all out and then show us > the simple upload recipe? > > My feeling is that the latest release should be on the package server. > daily bleeding edge builds could be there as well, under a different > name. > /* Begin Attachment */ From: Chong Yidong Subject: Re: Packages + elpa.gnu.org To: Jambunathan K Cc: emacs-de...@gnu.org Date: Fri, 08 Oct 2010 23:55:52 -0400 Message-ID: <87y6a86muv@stupidchicken.com> Jambunathan K writes: > 1. Who acts as a janitor for the elpa repository. Me. Ted Zlatanov also has access. We've both been pretty busy on other parts of Emacs lately, though, so there are a couple of packages that are in the pipeline for uploading (including AuCTEX). > 2. How does one upload packages - a mail drop to the maintainer, remote >update from within emacs - scp, ftp etc etc . (Is package-x.el's >package-upload-buffer and related configuration documented >somewhere.) Probably the easiest way to set this up is for someone on the org-mode team to upload the dailies to a server somewhere on the web, giving the tarball a deterministic name. Then, someone (probably me) will have to set up a cron job on elpa.gnu.org to check for that tarball each day, download it, and run `package-upload-file' to add it to the repository. > 3. Does the package manager expect that builtin packages be versioned in >a special way. For example, can the stable release be called 7.0.1 >while a daily snapshot be called 20101008? The package manager uses the most recent version of a package, as defined by `version-list-<'. > 4. Any general guidelines on what packages would be accepted there and >how often an update can happen. Are daily snapshots allowed. The main requirement is for package copyrights to be FSF assigned. I think providing dailies is fine. /* End Attachment */ > Thanks > > - Carsten > > > On Oct 8, 2010, at 12:38 PM, Carsten Dominik wrote: > >> >> On Oct 5, 2010, at 1:09 PM, Jambunathan K wrote: >> >>> >>> In the context of ELPA packages, I think there might be a need to >>> revisit how orgmode's version string is defined. >>> >>> For example, 7.01h wouldn't be successfully parsed by (version-to- >>> list >>> ...) which the package manager uses internally. >>> >>> So 7.01h could be mapped to 7.0.1.8 or 7.1.8. >> >> >> Hi Jambunthan, >> >> in what places would the version string have to be modified? >> Do I need to change the org.el variable org-version, or the string >> in the VERSION keyword in file headers, or where? >> >> - Carsten >> >>> >>> ,[ C-h f version-to-list RET ] >>> | version-to-list is a compiled Lisp function in `subr.el'. >>> | >>> | (version-to-list VER) >>> | >>> | Convert version string VER into an integer list. >>> | >>> | The version syntax is given by the following EBNF: >>> | >>> |VERSION ::= NUMBER ( SEPARATOR NUMBER )*. >>> | >>> |NUMBER ::= (0|1|2|3|4|5|6|7|8|9)+. >>> | >>> |SEPARATOR ::= `version-separator' (which see) >>> | | `version-regexp-alist' (which see). >>> | >>> | The NUMBER part is optional if SEPARATOR is a match for an element >>> | in `version-regexp-alist'. >>> | >>> | As an example of valid version syntax: >>> | >>> |1.0pre2 1.0.7.5 22.8beta3 0.9alpha1 6.9.30Beta >>> | >>> | As an example of invalid version syntax: >>> | >>> |1.0prepre2 1.0..7.5 22.8X3 alpha3.2 .5 >>> | >>> | As an example of version convertion: >>> | >>> |String VersionInteger List Version >>> |"1.0.7.5" (1 0 7 5) >>> |"1.0pre2" (1 0 -1 2) >>> |"1.0PRE2" (1 0 -1 2) >>> |"22.8beta3" (22 8 -2 3) >>> |"22.8Beta3" (22 8 -2 3) >>> |"0.9alpha1" (0 9 -3 1) >>> |"0.9AlphA1" (0 9 -3 1) >>> |"0.9alpha"(0 9 -3) >>> | >>> | See documentation for `version-separator' and `version-regexp- >>> alist'. >>> | >>> | [back] >>> ` >>> >>> Jambunathan K. >> >> - Carsten >> >> >> > > - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: "No link found" error during export of source block when headline has link
Hi Eric, I also confirm that the issue in my original post has been fixed. Thanks! -- Hsiu-Khuern. On Wed, Oct 6, 2010 at 7:52 AM, Eric Schulte wrote: > This issue should now be fixed. > > Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
