Hello,
Andreas Leha writes:
> Achim Gratz writes:
>
>> Andreas Leha writes:
>>> In this particular situation (the \subtitle will always be document
>>> specific) the latex class is not possible here -- I won't create latex
>>> classes per document.
>>
>> Classes can have arguments and the argum
Hello,
Mike McLean writes:
> On Wed, Mar 6, 2013 at 7:28 AM, Nicolas Goaziou wrote:
>
>> Vikas Rawal writes:
>>
>> >> CAPTION keyword above a source block applies to the source block only.
>> >> If the source block generates a table, you have to put a CAPTION above
>> >> it, as it will not inh
Hi Andreas,
Andreas Leha writes:
> But it looks very verbose to me. I expect the introduction to a
> scientific paper (with typically many \cite{}s) to look disrupted.
Each \cite{...} would be nothing more than
[[cite:A.N.Whitehead][A.N.Whitehead]] in the Org file.
The config happens in the #
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> Achim Gratz writes:
>>
>>> Andreas Leha writes:
In this particular situation (the \subtitle will always be document
specific) the latex class is not possible here -- I won't create latex
classes per docum
Hi Bastien,
Bastien writes:
> Hi Andreas,
>
> Andreas Leha writes:
>
>> But it looks very verbose to me. I expect the introduction to a
>> scientific paper (with typically many \cite{}s) to look disrupted.
>
> Each \cite{...} would be nothing more than
> [[cite:A.N.Whitehead][A.N.Whitehead]]
Jambunathan K writes:
> Bastien writes:
>
>> Hello Jambunathan,
>>
>> You are not welcome on this list anymore, please ban yourself.
>
> I asked you to exercise moderator controls. Why should I ban
> myself?
I am not a moderator of this list. And I would not like moderators to
exercise their
I was surprised by this behaviour.
Find a new org-mode file. Type "i)" and then hit M-Ret. The "i)" gets
renamed as "a)" and "b)" is added on the next line.
I would have expected that we get "ii)" on the next line and the "i)"
would be left alone.
Is this working as intended?
David Engster writes:
> Thanks. I've now pushed a further fix which should hopefully make things
> work with the new exporter. Julien, please let me know if it works.
Sorry, it doesn't.
I get the following when running org-caldav with the latest org-mode and
org-caldav from git.
--8<-
Bastien writes:
> Jambunathan K writes:
>
>> Bastien writes:
>>
>>> Hello Jambunathan,
>>>
>>> You are not welcome on this list anymore, please ban yourself.
>>
>> I asked you to exercise moderator controls. Why should I ban
>> myself?
>
> I am not a moderator of this list. And I would not li
Achim Gratz writes:
> Eric S Fraga writes:
>>> No, nothing complete yet. Here's what I have so far, some autoload
>>> definitions might still be there, but will error out due to the fact
>
>>> that their target files are not in load-path anymore.
>>
>> Thanks for this. I've incorporated it into
writes:
[...]
> I’ve got some mostly-working code that exports citations, only for
> latex, using a different approach (similar to Eric’s). I’ve cleaned it
> up some, and attached it as a patch to this email.
This looks quite nice.
I am unlikely to try it out, however, as my simple cite: (and
"Christopher W. Ryan" writes:
> Well, with the little test file I initially posted, things worked OK
> with org version 7.9.3f. But things are bit more complicated:
[...]
> Put cursor on
> * Hello
> above and then C-c C-e 1 d
Are you sure you are using the new exporter? This binding doesn't
Hi Paul,
Paul Rudin writes:
> Is this working as intended?
Yes, because roman enumeration is not supported by Org.
Org believes i) is the 9th item in an alphabetical list
and converts it to a) if it is the first one.
HTH,
--
Bastien
Andreas Leha writes:
> \footfullcite[prenote][postnote]{key}
What would prenote and postnote typically contain. Where would they
appear in the exported document - In the citation reference or in the
citation definition. Can the same key have different pre-note and
post-note attached to it.
I
Hi,
Same here. But the error is not in org-caldav, because it is triggered like
this:
(org-icalendar--combine-files nil "~/Desktop/ECM.org")
where ~/Desktop/ECM.org is a file with nothing but one headline.
/v
--
Vincent Beffara
On Thursday, March 7, 2013 at 10:13 , Julien Cubizolles wrot
Hi Aaron,
I now see where you and Eric go and this is good!
Here is a revised suggestion, allowing to add link types from withing
the #+LINK keyword.
1. Allow more syntax for #+LINK:
#+LINK: bib;%s;%s file:my.bib::%s org-bib-follow-link org-bib-export-link
If `org-bib-follow-link' is nil
Hello,
Vincent Beffara writes:
> Same here. But the error is not in org-caldav, because it is triggered like
> this:
>
> (org-icalendar--combine-files nil "~/Desktop/ECM.org")
>
> where ~/Desktop/ECM.org is a file with nothing but one headline.
I cannot reproduce it. Maybe a larger backtrace w
Hi Bastien,
On Thu, Mar 7, 2013 at 5:21 AM, Bastien wrote:
> Hi Aaron,
>
> I now see where you and Eric go and this is good!
>
> Here is a revised suggestion, allowing to add link types from withing
> the #+LINK keyword.
I suspect you may be targeting the wrong layer. Don't we want to use
org-l
Hi Aaron,
Aaron Ecay writes:
> I suspect you may be targeting the wrong layer. Don't we want to use
> org-link-protocols, not org-link-abbrev-alist? Protocols are already
> handled by the exporter, so there should be no need for a change like
> this one:
> [...]
I want to allow adding link pr
Here is an ECM.el file, run with emacs -Q triggers the crash:
(custom-set-variables
'(org-icalendar-store-UID t)
)
(setq-default debug-on-error t)
(add-to-list 'load-path "~/.emacs.d/el-get/org-mode/lisp")
(require 'ox-icalendar)
(org-icalendar--combine-files nil "~/Desktop/ECM.org")
without or
Hi Bastien,
On Thu, Mar 7, 2013 at 6:16 AM, Bastien wrote:
> I want to allow adding link protocols (what I called "adding link
> types") from #+LINK.
Hmm. I think I am beginning to understand your motivation for this.
> IIUC your proposal introduces some syntactic glue here:
> [[type:key;pre;p
> >> I wasn't clear. By "naming the results", I mean that you must provide
> >> your source block a "#+NAME: something" attribute, so the generated
> >> table gets a "#+RESULTS: something" attribute.
There is something strange happening. Cross-references to captions of
tables that are produced th
Vikas Rawal writes:
>> >> I wasn't clear. By "naming the results", I mean that you must provide
>> >> your source block a "#+NAME: something" attribute, so the generated
>> >> table gets a "#+RESULTS: something" attribute.
>
> There is something strange happening. Cross-references to captions of
Vincent Beffara writes:
> Here is an ECM.el file, run with emacs -Q triggers the crash:
>
> (custom-set-variables
> '(org-icalendar-store-UID t)
> )
> (setq-default debug-on-error t)
> (add-to-list 'load-path "~/.emacs.d/el-get/org-mode/lisp")
> (require 'ox-icalendar)
> (org-icalendar--combine-
Bastien writes:
> Hi Aaron,
>
> I now see where you and Eric go and this is good!
>
> Here is a revised suggestion, allowing to add link types from withing
> the #+LINK keyword.
>
> 1. Allow more syntax for #+LINK:
>
>#+LINK: bib;%s;%s file:my.bib::%s org-bib-follow-link org-bib-export-li
I have to admit I'm not yet experienced enough with org mode to know
about the new exporter versus the old. I've been trying to ignore the
conversations on the list about the new exporter, since, at least
until now, whatever org mode was doing was what I needed it to do.
I have org mode 7.9.3f. Do
It doesn't crash anymore, thanks!
OTOH when I ran org-caldav, it removed everything from the online calendar, and
it won't put anything back there ...
--
Vincent Beffara
On Thursday, March 7, 2013 at 13:56 , Nicolas Goaziou wrote:
> Vincent Beffara mailto:vbeff...@ens-lyon.fr)> writes:
>
>
> OTOH when I ran org-caldav, it removed everything from the online calendar,
> and it won't put anything back there ...
Mmmkay, something weird is happening. I create a headline with a date, and call
org-caldav. An UID is created, and the file looks like this:
*** Gayet, Damien : Une majoratio
>
> Could you provide an ECM?
>
See the attached dummy file.
Vikas
#+STARTUP: hidestars
#+TITLE: Title of the paper
#+DATE:
#+AUTHOR: name of author
#+COLUMNS: %25ITEM %TAGS %PRIORITY %T
#+property: exports results
#+property: session fbi
#+OPTIONS: H:2 toc:nil num:1
#+LaTeX_CLASS: article
*
... sorry for replying to myself like this - here is a patch that seems to
work:
diff --git a/org-caldav.el b/org-caldav.el
index 0383366..14cca8f 100644
--- a/org-caldav.el
+++ b/org-caldav.el
@@ -786,7 +786,7 @@ is no UID to rewrite. Returns the UID."
((re-search-forward "^UID:\\(orgsexp-[0-9
>
> Could you provide an ECM?
>
Please see the attached file.
Vikas
#+STARTUP: hidestars
#+TITLE: Title of the paper
#+DATE:
#+AUTHOR: name of author
#+COLUMNS: %25ITEM %TAGS %PRIORITY %T
#+property: exports results
#+property: session fbi
#+OPTIONS: H:2 toc:nil num:1
#+LaTeX_CLASS: article
*
Hi Nicolas,
I like Aaron's idea (maybe others proposed this too) of having
parameters in links:
[[file:my.bib::key&&prenote=my prenote&&postnote=my postnote]]
[[http://perdu.com&&title=You're lost?]]
This is orthogonal to my proposal of extending #+LINK to be able
to define new protocols (by al
Vikas Rawal writes:
>>
>> Could you provide an ECM?
I have always used something along these lines
#+label: crop-median
just before the table to define the target. This works for your ECM.
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55
Christopher W Ryan writes:
> I have to admit I'm not yet experienced enough with org mode to know
> about the new exporter versus the old. I've been trying to ignore the
> conversations on the list about the new exporter, since, at least
> until now, whatever org mode was doing was what I needed
Bastien writes:
> Hi all,
>
> with the advent of Org 8.0, a special effort needs to be made
> to keep the manual and Worg updated.
>
> I thought it would be nice to gather on IRC and focus on this
> together for a few hours, so here is a doodle:
>
> http://doodle.com/s7fhueeifaex54t8
>
> Also,
Prompted by Nicolas's recent addition of the LATEX_HEADER_EXTRA
directive, I would like to request another related feature. Just as we
have the related LATEX and BEGIN_LATEX directives, I would like to see a
BEGIN_LATEX_HEADER directive for multi-line LATEX_HEADER lines:
#+begin_src org
#+BEGIN_L
Thanks John. I will post the babel-related part of my .emacs when I
am back at the office, on the computer in question.
Could you try exporting just the * Hello subtree with C-c C-e 1 p ?
That's where I am experiencing the trouble, rather than with exporting
the whole document with C-c C-e p.
--
Achim Gratz writes:
> Carmine Casciato writes:
>> I downloaded the org-plus-contrib-20130304 package from the org-mode
>> elpa repo, and it does not seem to contain the contrib directory. Should
>> I be looking elsewhere for this?
>
> There is no contrib directory in this archive because ELPA pac
On Thu, Mar 7, 2013 at 9:54 AM, Christopher W Ryan wrote:
> Thanks John. I will post the babel-related part of my .emacs when I
> am back at the office, on the computer in question.
>
> Could you try exporting just the * Hello subtree with C-c C-e 1 p ?
> That's where I am experiencing the troubl
Nicolas Goaziou writes:
> For the same reason, caption here applies to the dynamic block, not to
> its contents.
This seems to be a common enough mistake and it is currently impossible
to put captions and other arguments on results blocks save with yet
another source block that produces the correc
Vikas Rawal writes:
>>
>> Could you provide an ECM?
>>
>
> Please see the attached file.
I cannot reproduce it, i.e. I get "\ref{crop-median}" in the output.
Regards,
--
Nicolas Goaziou
Bastien writes:
> I like Aaron's idea (maybe others proposed this too) of having
> parameters in links:
We've had some of this discussion about two years ago IIRC, so here I am
again: there's an internet standard for this kind of thing, it's called
URN/URI. If we adhere to this, we can at least h
Aloha Yagnesh Raghava Yakkala,
Yagnesh Raghava Yakkala writes:
> Hello Thomas,
>
>> These instructions assume more knowledge than I have. Could you be more
>> specific about "in the Org worktree"? Should I create a branch where I
>> do this? Or, should I put this in one of the upstream branches
Eric S Fraga writes:
> I believe that, if you are using 7.9.3f, you should be using the new
> exporter.
The question to answer is whether he's using the maint or the master
branch. I'd think the Op is using the 7.9.3f release, i.e. maint.
Bastien, I think it would make sense to clear up this con
Thomas S. Dye writes:
> The orgmanual now creates a pdf file, too, but one lacking the indexes
> and with links that look like they need another run through TeX.
In that case, texi2dvi and hence make should have signaled an error
(I've just pulled from your repo and it does).
> When I'm done runn
Achim Gratz writes:
> Thomas S. Dye writes:
>> The orgmanual now creates a pdf file, too, but one lacking the indexes
>> and with links that look like they need another run through TeX.
>
> In that case, texi2dvi and hence make should have signaled an error
> (I've just pulled from your repo and
Hello,
As discussed a few days ago, here is a document describing the complete
Org syntax as read by the parser. I also added some comments. I am going
to put the Org file on Worg, so anyone can update it and fix mistakes.
woow, this is awesome Nicolas, thank you!
- Carsten
On 7.3.2013, at 21:37, Nicolas Goaziou wrote:
> Hello,
>
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, s
Hello,
Achim Gratz writes:
> Nicolas Goaziou writes:
>> For the same reason, caption here applies to the dynamic block, not to
>> its contents.
>
> This seems to be a common enough mistake and it is currently impossible
> to put captions and other arguments on results blocks save with yet
> anot
Hello,
Eric S Fraga writes:
> Prompted by Nicolas's recent addition of the LATEX_HEADER_EXTRA
> directive, I would like to request another related feature. Just as we
> have the related LATEX and BEGIN_LATEX directives, I would like to see a
> BEGIN_LATEX_HEADER directive for multi-line LATEX_H
Assuming this is a recent regression, then if anyone from Org wants this
fixed in Emacs 24.3, they should investigate this very quickly and
suggest the _minimum_ change.
See also the possibly related, unanswered
http://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg00028.html
Lele Gaifax wr
Nicolas Goaziou writes:
> It's very easy to have a caption on the generated output: name the code.
> Hence, the following code block:
>
> #+NAME: calculation
> #+BEGIN_SRC emacs-lisp
> (+ 1 1)
> #+END_SRC
>
> will produce:
>
> #+RESULTS: calculation
> 2
>
> If you add a caption to the r
Hi Achim,
Achim Gratz writes:
> Bastien writes:
>> I like Aaron's idea (maybe others proposed this too) of having
>> parameters in links:
>
> We've had some of this discussion about two years ago IIRC, so here I am
> again: there's an internet standard for this kind of thing, it's called
> URN/U
Nicolas Goaziou writes:
> As discussed a few days ago, here is a document describing the complete
> Org syntax as read by the parser. I also added some comments. I am going
> to put the Org file on Worg, so anyone can update it and fix mistakes.
Wonderful. This will be really useful!
Regards,
A
Glenn Morris writes:
> Assuming this is a recent regression, then if anyone from Org wants this
> fixed in Emacs 24.3, they should investigate this very quickly and
> suggest the _minimum_ change.
The minimal fix is attached.
The other attachment is the full patch I wanted to apply to merge
Org
Bastien writes:
> I'm all for following established standards, but I'm not sure what is
> the concrete proposal here.
I don't have one yet, mainly because I'm fuzzy on what direction this
will take. I ask again to consider what's already out there and that's
mainly BibTeX and things that work in
> >> Could you provide an ECM?
> >>
> >
> > Please see the attached file.
>
> I cannot reproduce it, i.e. I get "\ref{crop-median}" in the output.
>
This is odd!! Please see the .tex file attached with this mail. This
is what I get. Any idea, how do I debug this?
Vikas
Nicolas Goaziou writes:
>> Prompted by Nicolas's recent addition of the LATEX_HEADER_EXTRA
>> directive, I would like to request another related feature. Just as we
>> have the related LATEX and BEGIN_LATEX directives, I would like to see a
>> BEGIN_LATEX_HEADER directive for multi-line LATEX_HE
Achim Gratz writes:
>> Do you mean using something like this
>>
>> [[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
>>
>> for the file: protocol
>
> This is a prime example of how _not_ to do this, IMHO. The file
> protocol is an established protocol that you shouldn't bolt any extra
> >>
> >> Could you provide an ECM?
> >>
> >
> > Please see the attached file.
>
> I cannot reproduce it, i.e. I get "\ref{crop-median}" in the output.
>
>
> Regards,
For me, it works if I change the value of org-babel-results-keyword
to NAME. Then the results block is produced with #+NAME:
Rasmus writes:
> Achim Gratz writes:
>
>>> Do you mean using something like this
>>>
>>> [[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
>>>
>>> for the file: protocol
>>
>> This is a prime example of how _not_ to do this, IMHO. The file
>> protocol is an established protocol that
Bastien wrote:
> Glenn Morris writes:
>
>> Assuming this is a recent regression, then if anyone from Org wants this
>> fixed in Emacs 24.3, they should investigate this very quickly and
>> suggest the _minimum_ change.
>
> The minimal fix is attached.
>
> The other attachment is the full patch I
Aloha all,
I think this behavior was introduced in the last week or so.
This in the Org file:
#+attr_latex: :height "2in"
[[file:saa-fig/wet-dry.jpeg]]
yields this in LaTeX output:
\begin{figure}[htb]
\centering
\includegraphics[width=.9\linewidth,height=2in]{saa-fig/wet-dry.jpeg}
\end{figure}
jeff stern wrote:
> Hi, all.
>
> i am noticing that in at least the latest git pull version of
> org-mode, org-special-ctrl-a/e (if setq'd to t) does not work
> correctly in Org-mode version 7.9.3f (release_7.9.3f-1447-gb2e1d6-git
> but does work correctly in Org-mode version 7.8.03
> (release_7
Nick Dokos writes:
> This might be a sign that you have a mixed installation.
M-x list-load-path-shadows RET
and ensure that your Org files come from only one directory. Keep
deleting (or renaming) Org installation directories until you have your
Org in only one directory.
Remember, to resta
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
Achim Gratz writes:
>> Do you mean using something like this
>>
>> [[file:my.bib&key=key;prenote=note1;postnote=note2][key]]
>>
>> for the file: protocol
>
> This is a prime example of h
The line mentioning Jambunathan K was committed by me not by the
maintainer. Don't be misled by what the annotate says, it shows who
made the most recent edit and not added the original line.
ps: If the maintainer is removing acknowledgements he should also remove
the files - both from regular o
Jambunathan K writes:
> ps: If the maintainer is removing acknowledgements he should also remove
> the files - both from regular org and contrib.
What this means is that if the file of which I am one of the author or
one of the principal author (if moved to GNU ELPA and re-distributed
with regul
Glenn Morris writes:
>> I assumed it was okay to fix bugs after the last pretest, is it so?
>
> No, it is not ok, and I don't know why you would think it is.
I missed the distinction between "pretest" and "release candidate".
> The reason for this policy is (obviously) to prevent inadvertently
Jambunathan K writes:
> What this means is that if the file of which I am one of the author or
> one of the principal author (if moved to GNU ELPA and re-distributed
> with regular Org distribution), I will vehemently argue that my efforts
> are acknowledged in the Org manual.
They are: http://o
Aloha Jambunathan,
Jambunathan K writes:
> Jambunathan K writes:
>
>> ps: If the maintainer is removing acknowledgements he should also remove
>> the files - both from regular org and contrib.
>
> What this means is that if the file of which I am one of the author or
> one of the principal auth
Hi,
t...@tsdye.com (Thomas S. Dye) writes:
>* Jambunathan K contributed the ODT exporter.
>
> Perhaps this is the place to flesh out your contributions? The line
> seems somewhat dated to me.
I update this line to include the rewrite of the HTML exporter.
If there are other important cont
On 2013-03-08 14:40 +0800, Bastien wrote:
> I find it hard to draw a clear line between regressions and bugs,
> especially since Org 7.9.x versions are way behind the current Org
> master branch.
I think org-mode is better in ELPA, a better distribution channel than
the core for things like org-mo
Leo Liu writes:
> On 2013-03-08 14:40 +0800, Bastien wrote:
>> I find it hard to draw a clear line between regressions and bugs,
>> especially since Org 7.9.x versions are way behind the current Org
>> master branch.
>
> I think org-mode is better in ELPA, a better distribution channel than
> the
On 2013-03-08 15:37 +0800, Bastien wrote:
> I strongly think otherwise: Emacs needs a good outline and editing
> tool. outline.el is not usable enough and I can see no other Emacs
> tool than Org-mode for exporting to HTML/LaTeX/ODT easily.
>
> I understand the temptation in terms of maintainance,
On 03/08/2013 02:40 PM, Bastien wrote:
I missed the distinction between "pretest" and "release candidate".
What's the difference between "pretest" and "release candidate"?
Doesn't the latter belong to the former? The rc1/rc1.1 was released on
the "pretest" directory.
--
Best regards, Xue F
Xue Fuqiao writes:
> On 03/08/2013 02:40 PM, Bastien wrote:
>> I missed the distinction between "pretest" and "release candidate".
>
> What's the difference between "pretest" and "release candidate"? Doesn't
> the latter belong to the former? The rc1/rc1.1 was released on the
> "pretest" directo
Achim Gratz writes:
> Bastien, I think it would make sense to clear up this confusion by
> tagging 8dd2bfc291 with version 7.9.9 or 8.0-pre or something like that
> (must be an annotated tag, of course). That'll help to easier determine
> who's using the new and the old exporter.
I used 8.0-pre
On 03/08/2013 03:37 PM, Bastien wrote:
I think org-mode is better in ELPA, a better distribution channel than
the core for things like org-mode. Bundling it in emacs doesn't help
anybody.
I strongly think otherwise: Emacs needs a good outline and editing
tool. outline.el is not usable enough
79 matches
Mail list logo
