Hi Eric,
Thank you so much for your reply and helpful suggestions. I looked into the
source of org-mode but as I am not familiar with elisp, I failed to get it.
Then I tried to not load my customized settings and tried org-mode export
again. And finally I found out it was due to another .el I
Eric Schulte eric.schu...@gmx.com writes:
Thanks for the detailed reproduction information in your original email,
it made this issue much easier to solve. I've just pushed up a fix,
please let me know if the problem continues.
Eric, seems to work perfectly now.
Thank you so much for your
Hello,
jeremiah.do...@gmail.com writes:
I've done a fair amount of reading (and-rereading) the manual, and
searching around, but my search skills are failing me and org-mode is
flexible enough that I figure that someone has either done this, or
there's something that makes it unnecessary
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Given a todo list in an org file, is there already a function, that
converts this list to an elisp list, that contains at least heading,
deadline and properties?
Create the following interactive function. This functions exports Org
file
Hi,
This patch implements warn time for org appt. It only works on emacs bzr
(the variable appt-warning-time-regexp appears in it). You need to add
the warntime in the text of the entry, like so :
* doctor warntime 10
2012-02-19 10:00
or
* doctor warntime 10 2012-02-19 10:00
The patch is
Achim Gratz strom...@nexgo.de writes:
Eric Schulte eric.schu...@gmx.com writes:
It will be up to the authors of individual tests to remove tangled and
exported files. Ideally we can patch each test to clean up after
itself. Perhaps we should provide a test macro which accepts a list of
Just to be safe, I nuked my org-mode directory and re-cloned from the
git repository: I'm now at release_7.8.03.386.g2239d (I was at
release_7.8.03-351-g47eb3 previously). Is there a more recent
version? I also removed the org directory that came with the packaged
version of emacs, just in
Eric Schulte eric.schu...@gmx.com writes:
I should have been more clear. I'm thinking that this would be a macro
used /within/ unit tests so that testers could specify what files will
be created (test writers should be able to predict the file names
created by their tests) and then the macro
On 02/19/2012 08:48 AM, Eric Schulte wrote:
Just to be safe, I nuked my org-mode directory and re-cloned from the
git repository: I'm now at release_7.8.03.386.g2239d (I was at
release_7.8.03-351-g47eb3 previously). Is there a more recent
version? I also removed the org directory that came with
Hello,
I'd like to introduce a new type of internal links, namely ref links.
Since any element can now have a #+name: something affiliated keyword,
it would be practical to have a way to go straight to that name, from
anywhere in the buffer. The following patch implements
a [[ref:something]]
On 02/19/2012 09:40 AM, Daniel Drake wrote:
On 02/19/2012 08:48 AM, Eric Schulte wrote:
Just to be safe, I nuked my org-mode directory and re-cloned from the
git repository: I'm now at release_7.8.03.386.g2239d (I was at
release_7.8.03-351-g47eb3 previously). Is there a more recent
version? I
On 02/19/2012 10:28 AM, Daniel Drake wrote:
On 02/19/2012 09:40 AM, Daniel Drake wrote:
On 02/19/2012 08:48 AM, Eric Schulte wrote:
Just to be safe, I nuked my org-mode directory and re-cloned from the
git repository: I'm now at release_7.8.03.386.g2239d (I was at
release_7.8.03-351-g47eb3
Hi,
I think it's a great idea, as I've wanted to do it myself :-) , but
I'm glad it's in competent hands instead.
Me, I don't see any problem with a [[ref:something]] syntax. It's the
obvious org-native, cross-backend replacement for \ref. The
[[protocol:something]] syntax already widens
I think it's a good idea, and would suggest this:
* If it is not going to have features added, then [[ref:asdf]] is OK
* If it /is/ going to have features added, then I recommend ES/US
ES/US is extensible syntax / universal syntax, a specific proposal for
an orthogonal and future-proof
Hello,
Christian Moe m...@christianmoe.com writes:
Me, I don't see any problem with a [[ref:something]] syntax. It's the
obvious org-native, cross-backend replacement for \ref. The
[[protocol:something]] syntax already widens the notion of link to
shell: and elisp: links, so I wouldn't worry
Hello,
Samuel Wales samolog...@gmail.com writes:
I think it's a good idea, and would suggest this:
* If it is not going to have features added, then [[ref:asdf]] is OK
* If it /is/ going to have features added, then I recommend ES/US
ES/US is extensible syntax / universal syntax, a
On 19.2.2012, at 19:08, Nicolas Goaziou wrote:
Hello,
I'd like to introduce a new type of internal links, namely ref links.
Since any element can now have a #+name: something affiliated keyword,
it would be practical to have a way to go straight to that name, from
anywhere in the
On Sun, Feb 19, 2012 at 08:41:45PM +0100, Nicolas Goaziou wrote:
Suggestion: On export, how about enabling automatic element
descriptions for references following the type:name convention, so
that e.g. just
: in [[ref:tab:numbers]] we can see...
would expand to
in Table 2 we
On 2/19/12 8:41 PM, Nicolas Goaziou wrote:
That's another possibility, but I'd rather follow LaTeX usage. I think
it gives user more latitude in the end. Indeed, You don't have to think
about a name prefix ; you can also have constructs like Tables
[[ref:table1]], [[ref:table2]] and
A further followup, at the risk of descending into minutia. The
culprit seems to be the emacs function string-to-number.
On my 32-bit Arch machine:
(string-to-number 123456789): 123456789 (#o726746425, #x75bcd15)
(string-to-number 987654321): 987654321.0
GNU Emacs 23.4.1
On 2012-02-19, Nicolas Goaziou n.goaz...@gmail.com wrote:
Ok, I found the thread[1] about extensible syntax for links.
Again this isn't just for links and if your syntax does all you ever
anticipate, then I like it. I am talking about the future and the
difficulty of adding ad-hoc syntax fore
On Sun 19 Feb 2012 12:46:15 PM PST, Eric Schulte wrote:
A further followup, at the risk of descending into minutia. The
culprit seems to be the emacs function string-to-number.
On my 32-bit Arch machine:
(string-to-number 123456789): 123456789 (#o726746425, #x75bcd15)
(string-to-number
Eric Schulte eric.schu...@gmx.com writes:
A further followup, at the risk of descending into minutia. The
culprit seems to be the emacs function string-to-number.
On my 32-bit Arch machine:
(string-to-number 123456789): 123456789 (#o726746425, #x75bcd15)
(string-to-number 987654321):
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
There are probably a lot of ways to achieve this with included tools.
For example, on a per file basis, you may use radio targets:
#+begin_src org
Contempt for happiness is usually contempt for other people's happiness,
and is an elegant
If I have something like:
(setq org-agenda-custom-commands
'((Q Q-Who todo IMPLEMENT ((org-agenda-todo-list-sublevels t)))
))
in my .emacs
and I have
*** IMPLEMENT explore slash type [1/3]
- [X] Explore checkbox list
- [ ] Look at the export
- [ ] And so on
*** IMPLEMENT
FTR, I'm just commenting based on experience with a testing harness for
a completely unrelated piece of software.
Achim Gratz strom...@nexgo.de writes:
Eric Schulte eric.schu...@gmx.com writes:
I should have been more clear. I'm thinking that this would be a macro
used /within/ unit tests so
Hi Eric
My guess is that during export you get a message along the lines of
htmlize is required for export. Try explicitly loading htmlize.el
(in the contrib/lisp directory of org) and then re-exporting ...
You're spot on - importing htmlize.el did the trick. However, before importing
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
Why are you saying it is not a full replacement for \ref{something}?
There are still a few limitations. For example, you cannot reference
a precise list item since items do not accept affiliated keywords.
It is better than that because
lbml...@hethcote.com writes:
If I have something like:
(setq org-agenda-custom-commands
'((Q Q-Who todo IMPLEMENT ((org-agenda-todo-list-sublevels t)))
))
in my .emacs
and I have
*** IMPLEMENT explore slash type [1/3]
- [X] Explore checkbox list
- [ ] Look at the export
Links with descriptions do not always display properly in tables. If I
execute org-toggle-link-display, the full link text gets displayed, but
table alignment is messed up. Executing org-table-align makes things
look pretty again. I think it should happen automatically.
Emacs : GNU Emacs
On Sun, 19 Feb 2012, Bernt Hansen wrote:
lbml...@hethcote.com writes:
If I have something like:
(setq org-agenda-custom-commands
'((Q Q-Who todo IMPLEMENT ((org-agenda-todo-list-sublevels t)))
))
Hi Louis,
I think we need more information. In a todo agenda view you should
Thanks, Nick! It works, though it works only to the specified file(s)
by overruling the original org-store-link-functions. Ideally, it would
be great if in the normal stored org link, line number could be
included in the link and would be ripped off from the text to search
the linked file.
On
Not To Miss not.to.m...@gmail.com wrote:
Thanks, Nick! It works, though it works only to the specified file(s)
by overruling the original org-store-link-functions.
Yes, org marches down the link handlers and takes the first positive
response as the answer. You can make the function arbitrarily
On Feb 20, 2012, at 1:51 AM, Nicolas Goaziou wrote:
Hello,
Carsten Dominik carsten.domi...@gmail.com writes:
Why are you saying it is not a full replacement for \ref{something}?
There are still a few limitations. For example, you cannot reference
a precise list item since items do not
Hi all,
why is it, that I can not use this code in sh blocks (I get sh: 2: Bad
substitution), even though it is valid when I run the tangled
script? Is this a known thing?
#+begin_src sh :shebang #!/bin/bash :tangle test.sh
for i in *.org; do
echo cp $i ${i/%.org/.bak.org}
done
35 matches
Mail list logo
