Eric Schulte schulte.e...@gmail.com writes:
Dieter Wilhelm, H. die...@duenenhof-wilhelm.de writes:
Dear (),
I've got a rather long argument list and it doesn't look good to
supply all the arguments in one line, could somebody please implement
#+header arguments for #+call like in the
Eric Schulte schulte.e...@gmail.com writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Andreas Leha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 19 Jul 2013 13:00:26 +0200
Rasmus ras...@gmx.us wrote:
Eric S Fraga e.fr...@ucl.ac.uk writes:
Renato renn...@gmail.com writes:
Hi, I've customized org-latex-packages-alist and added the package
babel, with option italian, however
Jambunathan K kjambunat...@gmail.com writes:
#+toc: headlines :levels 4
(:toc headlines :levels 4)
Btw, I forgot to mention that BIBLIOGRAPHY is itself a table of
citations.
Nicolas
Getting Citation right to cater to general needs is going to be complex.
This is mainly because
1. Org's object syntax is very rudimentary and not extensible
2. real-world citations may need some annotations page number etc.
I think it is good to *atleast make a move* in
I understand. You can still use ox-bibtex.el for now, and just ignore
all the [[cite:...]] part.
Each citation processor should reside in it's own file. So ox-jabref.el
is the right place for my changes.
It seems that you are not interested in introducing ox-cite.el or a
make-shift
I have finalized the JabRef + ODT export. The changes can be pulled
from my own repo at
HomePage: http://repo.or.cz/w/org-mode/org-kjn.git
Pull URL: git://repo.or.cz/org-mode/org-kjn.git
http://repo.or.cz/r/org-mode/org-kjn.git
For purposes of quick testing,
Jambunathan K kjambunat...@gmail.com writes:
Will it go as part of in text or will it go in to References list or
both. For command line based processing, I see foresee issues with:
1. Multiple keys.
2. Stuff like Ibid.
3. Sort order of keys.
4. Numbering of entries.
To
Nicolas Goaziou n.goaz...@gmail.com writes:
before discussing (again) citations syntax
I understand that talking about citations syntax will lead to
bike-shedding. Every one - including me - seem to have an (un)informed
opinion of it. The intent of the mail - as the subject - says is to
I am not sure how many people will read this or make sense out of it.
Anyways, here I go.
Rasmus ras...@gmx.us writes:
- textcite k :pre x :post y → K (pre, year, post)
- parencite k :p x :post y→ (pre, K, year post)
- cite k :pre x :post y → K pre K year post
Rasmus ras...@gmx.us writes:
The system should exhibit some flexibility supporting e.g. notes,
parencite (prenote, key, year, postnote) and textcite key (prenote,
year, postnote). But there could be others. E.g. someone mentioned
using DOIs etc.
I am not a scholar. I have never used
(Fixed up the subject and CC line.)
As for #+ATTR_BACKEND lines, they *must* be prefixed with the citation
processor's name.
It is unlikely that there will be a convergence of what Org-wide
':citation-style' values are. In that case, they can be converted to
citation-processor specific style.
Let me state unequivocally that I am willing to co-operate .
Nicolas Goaziou n.goaz...@gmail.com writes:
I'm just pointing out two things:
- ox-bibtex will have to be implemented differently (e.g., no more
defadvices).
Citation are obivously objects, whatever be their underlying
As expressed elsewhere I think
[cite:key :pre xxx :post yyy :mycrazykey zzz]
is the most desirable syntax.
Where would the pre, post text would go.
Will it go as part of in text or will it go in to References list or
both. For command line based processing, I see foresee issues with:
Jambunathan K kjambunat...@gmail.com writes:
Thorsten Jolitz tjol...@gmail.com writes:
seems to be a bigger project
No, it is not. Unless you consider adding these a bigger project.
(defvar org-message-level)
(defun org-message (level other args)
)
Dear Eric,
please find attached a patch, to describe the different standard values for
system-wide header arguments in the manual.
Hope that might help to avoid confusion in the future.
All the best
Torsten
On 25 July 2013 00:30, Eric Schulte schulte.e...@gmail.com wrote:
Torsten Wagner
This helps a lot. Thanks!
Happy this worked out.
Now, I will this into all my org files.
Check out the library of babel of things that you want to have globally
available.
Best,
Cheers,
Andreas
--
Eric Schulte
http://cs.unm.edu/~eschulte
Torsten Wagner torsten.wag...@gmail.com writes:
Dear Eric,
please find attached a patch, to describe the different standard values for
system-wide header arguments in the manual.
Hope that might help to avoid confusion in the future.
All the best
Thanks for sending this along. Would you
I don't believe there are any restrictions on the number of header lines
before a code block.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
This helps a lot. Thanks!
Happy this worked out.
Now, I will this into all my org files.
Check out the library of babel of things that you want to have globally
available.
Thanks for the hint. If I put it there, I still have to
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
This helps a lot. Thanks!
Happy this worked out.
Now, I will this into all my org files.
Check out the library of babel of things that you want to have globally
available.
Sorry for breaking the thread, i deleted the prior message.
On 2013-07-23 08:25, Sebastien Vauban wrote:
See the contents of the following vars:
- `org-babel-default-header-args' for source blocks
- `org-babel-default-inline-header-args' for inline source blocks
-
Hi,
I'm making a very simple org-document -- a packing list for a trip.
It has entries like
- 4 mugs
- for sleeping bags
- 4 thermarest pads
I'd like to replace the numbers there by a variable -- so if I make a
list for 4 people, the number displayed will be '4'; but if the list
is for 2
Hi, I found an inventive solution by Suvayu to discard headlines from export
here [1], but the 8.0+ solution throws an error in my environment.
(defun sa-ignore-headline (contents backend info)
Ignore headlines with tag `ignoreheading'.
(when (and (org-export-derived-backend-p backend 'latex
Hi,
I have a few functions defined with babel, which need to work on an list of
tables.
At the moment I use something like :var table1=name1 :var table2=name2
etc.
As you can see this is rather inflexible.
I am looking for a way to receive a list of tables, whereas table[0] would
refer to the
Hello,
David Maus dm...@ictsoc.de writes:
IIRC org-link-escape is not used to create URLs but to escape
characters in a link that would otherwise conflict with Orgmode syntax
(e.g. square brackets).
Org applies percent escaping to a link before
it is stored in the buffer and applies
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Matt Price mopto...@gmail.com writes:
Hi,
I'm making a very simple org-document -- a packing list for a trip.
It has entries like
- 4 mugs
- for sleeping bags
- 4 thermarest pads
I'd like to replace the numbers there by a variable -- so if I make a
list for 4 people, the number
So I've been working on this issue, still don't have it quite worked out
like I would want. What I would like to do is either)
Have template that inserts itself under the LAST entry in the target file
for a given headline
OR
composes the right strings to use file+olp to find the specific
Hello Subhan,
On Thu, Jul 25, 2013 at 03:29:10PM -0700, Subhan Tindall wrote:
Have template that inserts itself under the LAST entry in the target file
for a given headline
What problem do you have with the above? Can you give us a minimal
example?
composes the right strings to use file+olp
Yes, you are correct, file+datetree does not do this. A while ago I
suggested a file+datetree+headline type function be added, but it was not
received well.
I attempted a function for use with file+function, but couldn't get it
quite working.
I'm not quite sure how to use org-map-entries to find
Matt Price mopto...@gmail.com writes:
Hi,
I'm making a very simple org-document -- a packing list for a trip.
It has entries like
- 4 mugs
- for sleeping bags
- 4 thermarest pads
I'd like to replace the numbers there by a variable -- so if I make a
list for 4 people, the number
Hi,
Thorsten Jolitz writes:
Matt Price mopto...@gmail.com writes:
Hi,
I'm making a very simple org-document -- a packing list for a trip.
It has entries like
- 4 mugs
- for sleeping bags
- 4 thermarest pads
I'd like to replace the numbers there by a variable -- so if I make a
list
At Thu, 25 Jul 2013 23:46:34 +0200,
Nicolas Goaziou wrote:
Hello,
David Maus dm...@ictsoc.de writes:
The bottom-line: Org creates link programmatically (org-store-link)
and needs a mechanism to protected conflicting characters. It chose
percent-escaping and in order to preserve the
34 matches
Mail list logo
