Vaidheeswaran C writes:
> On Tuesday 24 February 2015 11:37 AM, Thomas S. Dye wrote:
>> Aloha Vaidheeswaran C,
>>
>> Vaidheeswaran C writes:
>>
>>> On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
Vaidheeswaran C writes:
> Often times there is a difference between what
On Tuesday 17 February 2015 10:48 PM, Richard Lawrence wrote:
Another, more serious reason is that I work in a field where some
journals do not accept LaTeX submissions, or disprefer them; so
having some citation support in ODT export is important.)
You are lobbying for two things:
1. An impr
On Tuesday 24 February 2015 11:37 AM, Thomas S. Dye wrote:
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
Vaidheeswaran C writes:
Often times there is a difference between what is possible and what is
the common practice. So,
1
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
> On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
>> Vaidheeswaran C writes:
>>
>>> Often times there is a difference between what is possible and what is
>>> the common practice. So,
>>>
>>> 1. How often do you intermix in-text and par
I have an old org file, with some source blocks that create a table with some
hyperlinks like [[file:../receipts/2015/02/aj140212_1.pdf][19998-DUPLT]]
(the file is in receipts subdirectory of the parent directory).
Export from the org file used to work fine. But just now, these paths are
On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
Vaidheeswaran C writes:
Often times there is a difference between what is possible and what is
the common practice. So,
1. How often do you intermix in-text and parenthetical styles.
Every day?
Ok.
2. Can the document author re
Vaidheeswaran C writes:
> Often times there is a difference between what is possible and what is
> the common practice. So,
>
> 1. How often do you intermix in-text and parenthetical styles.
Every day?
> 2. Can the document author re-word his work in such a way that an
>in-text or parenthe
On Tuesday 24 February 2015 04:55 AM, Richard Lawrence wrote:
Vaidheeswaran C writes:
But whatever style is chosen, I would still think that the fact that the
citation is in-text rather than parenthetical, and that it has a prefix
and suffix, should be represented in the output.
1. When you
On Tuesday 24 February 2015 08:56 AM, Alexis wrote:
For examle, one might have a citation style like:
[Smith 2001]
which in certain contexts is expected to have a presentation style of
'bolded'.
So what i understand Vaidheeswaran to be asking is: Please don't code
things such that presentation
On 2015-02-24T10:25:39+1100, Richard Lawrence said:
RL> Vaidheeswaran C writes:
>>> But whatever style is chosen, I would still think that the
>>> fact that the citation is in-text rather than parenthetical,
>>> and that it has a prefix and suffix, should be represented in
>>> the output.
>
Probably there is some more elegant way but if you run this on a link,
you get the two pieces I think. In a filter or exporter, you might
replace (org-element-context) with the link element/object
#+BEGIN_SRC emacs-lisp
(defun parse-link ()
(interactive)
(message-box "%s"
(cons
;; path
(org
Hi all,
so I have this:
[[file:whatever.org][Some link]]
How do I extract bith parts of this link programmatically?
My use case is that I have an Org tree of links, and I want to export
them to certain XML format.
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Facult
On 2015-02-18, at 15:19, Eric S Fraga wrote:
> Support for tikz is there implicitly in that there is support for
> LaTeX. I use tikz all the time.
Yes, but I wanted to be able both to see the diagram in the Org file
itself /and/ to export it properly to LaTeX. (It seems that your
solutions di
Vaidheeswaran C writes:
>> But whatever style is chosen, I would still think that the fact that the
>> citation is in-text rather than parenthetical, and that it has a prefix
>> and suffix, should be represented in the output.
>
> 1. When you choose 'style' (Chicago etc.) wouldn't be one of in-te
look into org-agenda-prefix-format. However, you can also change the
category of your org files by putting
#+CATEGORY: MYCAT
at the very top of your org files, and that decouples the category
(the first column in agenda) from the filename.
On Mon, Feb 23, 2015 at 11:59 AM, David Belohrad wrote:
Dear All,
I'm using quite long filenames for my org files
(e.g. emails_sent-pcbe13433.org). I get into troubles when constructing
an agenda as there is not enough space between the first filename
column and second time column. Is there any way how to adjust the widths
of the columns in the agenda?
Hi Nicolas,
On 2015-02-23 at 14:32, Nicolas Goaziou
wrote:
Ken Mankoff writes:
It would be nice to have an [[Org mode link]]
# in a line that is [[commented]] and still
be able to see that link. Currently, there is no visual
indication that the link exists, although it still does work.
Nicolas Goaziou writes:
> Hello,
[]
> Indeed. This should be fixed in
> ad7b7efcdc2e0803cbf0257bb2588c8e8e1cac29.
>
> If fall-backs to a plain string.
>
> Thank you.
Thanks to you for taking care so quickly!
Best,
Daniele
It would be nice to have an [[Org mode link]]
# in a line that is [[commented]] and still
be able to see that link. Currently, there is no visual indication
that the link exists, although it still does work.
-k.
Fabulous! Thanks!
Nicolas Goaziou writes:
> Hello,
>
> John Kitchin writes:
>
>> I agree. Even for experienced people, this is pretty annoying. Something
>> as simple as
>>
>>
>> #+BEGIN_SRC emacs-lisp
>> '((1 . nil) (2 . 3))
>> #+END_SRC
>>
>> fails with a cryptic error. While this works fine.
Leandro Noferini writes:
> What is an ECM?
French acronym for minimal complete example.
>> or even the full file if it doesn't contain sensitive information?
>
> I could send you privately, not in list: nothing really sensitive, job
> appointments but not to be indexed in the internet for the e
Vaidheeswaran writes:
>> We haven't really discussed how styles should be specified (yet), or the
>> formatting of bibliographies. But we have been discussing a syntax that
>> lets you specify those formatting properties which commonly differ
>> between individual citations.
>
> IMO, it is bette
On 2015-02-23 at 09:02, Ken Mankoff wrote:
On 2015-02-23 at 03:35, Nicolas Goaziou
wrote:
Hmm. It is happening on the latest melpa install. Or maybe on an
earlier version and I'm only seeing it now. I run melpa, no git
versions.
There is a function in ORG-NEWS that will repair old docume
>
> thanks for the explanation.
>
> Unfortunately my lisp knowledge is too limited to understand you. As a
> naive org-mode user, if possible I do not want to be exposed to org
> internals error, especially the confusing ones, where the custom code
> works fine. Maybe we can get a warning instead
On 2015-02-23 at 10:03, Rainer M Krug wrote:
Just confirmed here - works here:
Org-mode version 8.3beta (release_8.3beta-846-g38ab8b
@/Users/rainerkrug/.emacs.d/org-mode/lisp/)
Yes it does. I've upgraded to 8.3 from git.
Thanks,
-k.
hymie! writes:
> Sorry to resurrect an old thread, but this isn't actually working.
>
> hymie! lactose.homelinux.net> writes:
>
>>
>> hymie! lactose.homelinux.net> writes:
>>
>> > So while I strongly prefer the exported version of
>> > - ~command1~
>> > - ~command2~
>> > - ~command3~
>> > it'
Ken Mankoff writes:
> On 2015-02-23 at 09:39, Rainer M Krug wrote:
I'm working with my literate init file (emacs.org), and would like
to have certain sections not tangle. I currently do this with
":tangle no" at the SRC block level. Is it possible to control
tangling with ta
So the documentation says
>You can make words *bold*, /italic/, _underlined_, =verbatim= and ~code~,
>and, if you must, ‘+strike-through+’. Text in the code and verbatim string is
>not processed for Org mode specific syntax, it is exported verbatim.
However, that is not the behavior I am seeing.
Sorry to resurrect an old thread, but this isn't actually working.
hymie! lactose.homelinux.net> writes:
>
> hymie! lactose.homelinux.net> writes:
>
> > So while I strongly prefer the exported version of
> > - ~command1~
> > - ~command2~
> > - ~command3~
> > it's hard to copy-n-paste with the
Daniele Pizzolli writes:
> Hello Ken,
>
> Ken Mankoff writes:
>
>> I'm working with my literate init file (emacs.org), and would like to
>> have certain sections not tangle. I currently do this with ":tangle no"
>> at the SRC block level. Is it possible to control tangling with tags at
>> the hea
On 2015-02-23 at 09:39, Rainer M Krug wrote:
I'm working with my literate init file (emacs.org), and would
like to have certain sections not tangle. I currently do this
with ":tangle no" at the SRC block level. Is it possible to
control tangling with tags at the header level?
If I am not
Daniele Pizzolli writes:
> Hello Ken,
>
> Ken Mankoff writes:
>
>> I'm working with my literate init file (emacs.org), and would like to
>> have certain sections not tangle. I currently do this with ":tangle no"
>> at the SRC block level. Is it possible to control tangling with tags at
>> the hea
Nicolas Goaziou writes:
[...]
>> In the Message buffer I see this message:
>>
>> org-ascii--table-cell-width: Args out of range: [nil], 1
>>
>> The other files are exported normally and the only difference I can see
>> is in fact the file with error has appointments lasting over the
>> midnight
On 2015-02-23 at 03:35, Nicolas Goaziou wrote:
> Ken Mankoff writes:
>
>> I have found many task with duplicate PROPERTIES drawers. I saw mention on
>> the list that, "...it will be invalid for a LOGBOOK to appear before
>> PROPERTIES in Org 8.3."
>>
>> It seems that tasks don't have propertie
John Kitchin writes:
> I am pretty sure this is a long-standing "feature".
>
> Try this:
> #+BEGIN_SRC emacs-lisp :results raw
> (org-babel-do-load-languages
> 'org-babel-load-languages
> '((emacs-lisp . nil)
> (R . t)))
> #+END_SRC
>
> I have never been able to use a babel block that outputs a
Hello,
I remember that sh was renamed to shell some time ago.
But shell sometimes does not work, while sh does.
Is there a difference between the two (and when i should use one over
another?) or is it a bug?
The minimal example follows:
#+PROPERTY: header-args:shell :dir /vagrant@127.0.0.1:/v
I am pretty sure this is a long-standing "feature".
Try this:
#+BEGIN_SRC emacs-lisp :results raw
(org-babel-do-load-languages
'org-babel-load-languages
'((emacs-lisp . nil)
(R . t)))
#+END_SRC
I have never been able to use a babel block that outputs a list of cons
cells without explicitly set
Hello,
my attempt to use org-mode for both interactive presentation and final
report was unsuccessful due to a series of bugs and nuisances.
Fortunately I can use the result of tangle. Will report the issues
encountered to the list in the next few days.
Here is a minor one.
The following code,
Hello,
Leandro Noferini writes:
> I found an error trying to export an org file to ics format also via the
> standard command Ctrl-C-Ctrl-E and via org-caldav sync process.
>
> In the Message buffer I see this message:
>
> org-ascii--table-cell-width: Args out of range: [nil], 1
>
> The other fi
Ciao a tutti,
I found an error trying to export an org file to ics format also via the
standard command Ctrl-C-Ctrl-E and via org-caldav sync process.
In the Message buffer I see this message:
org-ascii--table-cell-width: Args out of range: [nil], 1
The other files are exported normally and the
Hello,
Xavier Maillard writes:
> I am trying to publish my org project but I am lost in the way I can
> tweak my projects.
>
> Is there some good tutorial I can follow step by step in order to
> publish several files at once ?
>
> My site tree is like this:
>
> web/
> ├── Makefile
> ├── css
> │
Hello,
Ken Mankoff writes:
> I have found many task with duplicate PROPERTIES drawers. I saw mention
> on the list that, "...it will be invalid for a LOGBOOK to
> appear before PROPERTIES in Org 8.3."
>
> It seems that tasks don't have properties by default, and if I LOG an
> item, I get a LOGBO
Hi,
Xavier Maillard writes:
> Hello,
>
> I am trying to publish my org project but I am lost in the way I can
> tweak my projects.
>
> Is there some good tutorial I can follow step by step in order to
> publish several files at once ?
>
> My site tree is like this:
>
> web/
> ├── Makefile
> ├── c
43 matches
Mail list logo
