Dear all,
I have release version 7.02 or Org-mode. Thanks to all who
have contributed!
Enjoy
- Carsten
Changes in version 7.02
Incompatible Changes
~
Code block hashes
==
Due to changes in the code resolving code block header arguments
hashing of code b
"Eric Schulte" writes:
>
> Although I'm not familiar with using Calc as anything more than a 1-off
> calculator in the bottom of the frame (i.e. M-x calc) this sounds like a
> good approach to using calc to execute code blocks.
>
Did I mention I'm not familiar with Calc.
I've thrown together a
Many thanks to all of you for figuring this out and fixing it. I can
confirm that internal and external links both work in the pdf file
compiled from the Org-mode LaTeX export, which is way cool and seems
miraculous to a dirt archaeologist.
All the best,
Tom
On Oct 28, 2010, at 7:01 PM, N
"Eric Schulte" writes:
> Łukasz Stelmach writes:
>
>> Richard Riley writes:
>>
>>> "Eric Schulte" writes:
>>>
Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
It's a very nice little utility for giving presentations using Emacs as
the display engine.
>> [...]
Nick Dokos wrote:
> Thomas S. Dye wrote:
>
> > ...
> > I did hit on a revision that was neither good nor bad:
> >
> > commit 8562273b272024a630a582b0e1b94c481d8abeec
> > Author: Eric Schulte
> > Date: Sat Oct 16 13:21:47 2010 -0600
> >
> > ob-ref: don't forget arguments to referenced c
Carsten Dominik writes:
> On Oct 29, 2010, at 5:22 AM, Jambunathan K wrote:
>
>> "Thomas S. Dye" writes:
>>
>>> Aloha Jambunathan K.,
>>>
>>> Yes, thanks for that suggestion. It should work on your example, but
>>> it breaks external links, like this:
>>>
>>> \hyperref[http://www.ctan.org/tex-a
Sébastien Vauban writes:
> - I did not see any image
I think inline images should be working with the latest version
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/
Jambunathan K writes:
> "Eric Schulte" writes:
>
>> Jambunathan K writes:
>>
>>> "Eric Schulte" writes:
>>>
Hi,
Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
It's a very nice little utility for giving presentations using Emacs as
the display engin
On Oct 29, 2010, at 5:22 AM, Jambunathan K wrote:
"Thomas S. Dye" writes:
Aloha Jambunathan K.,
Yes, thanks for that suggestion. It should work on your example, but
it breaks external links, like this:
\hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/
]{KOMA-scri
"Thomas S. Dye" writes:
> Aloha Jambunathan K.,
>
> Yes, thanks for that suggestion. It should work on your example, but
> it breaks external links, like this:
>
> \hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/
> ]{KOMA-script}
>
> External links require the \href{}{
Thomas S. Dye wrote:
> ...
> I did hit on a revision that was neither good nor bad:
>
> commit 8562273b272024a630a582b0e1b94c481d8abeec
> Author: Eric Schulte
> Date: Sat Oct 16 13:21:47 2010 -0600
>
> ob-ref: don't forget arguments to referenced code blocks
>
> * lisp/ob-ref.el (or
> FWIW, I have a home-brewed perl script that converts latex documents to
> org-mode files. Loosely based on latex2doc[1], it uses a latex style
> file (generated by the perl script) to markup the pdf output (e.g.
> asterisks for section headings, etc.). The org-formatted pdf is then
> converted to
Aloha Jambunathan K.,
Yes, thanks for that suggestion. It should work on your example, but
it breaks external links, like this:
\hyperref[http://www.ctan.org/tex-archive/macros/latex/contrib/koma-script/
]{KOMA-script}
External links require the \href{}{} command. It appears the LaTeX
"Eric Schulte" writes:
> Jambunathan K writes:
>
>> "Eric Schulte" writes:
>>
>>> Hi,
>>>
>>> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
>>> It's a very nice little utility for giving presentations using Emacs as
>>> the display engine. Obviously I was aghast to learn
Carsten
>
> (version-to-list "7.02") -> (7 2)
> (version-to-list "7.20") -> (7 20)
>
> so it seems to me that if we keep two-digit numbers, there will be no
> problem at all.
>
> #+begin_src emacs-lisp
> (version-list-= (version-to-list "7.02") (version-to-list "7.20"))
> #+end_src
Yes, I agr
Thomas
There was a hint at possible solution (or atleast a partial solution) in
my original post. Did you try it before jumping in to rough waters or
digging deeper?
Do
,
| M-x customize-variable RET org-export-latex-hyperref-format'
`
so that your .emacs has an entry like this
,---
On Oct 28, 2010, at 12:35 PM, Nick Dokos wrote:
Thomas S. Dye wrote:
On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote:
This is a regression. release-7.01h is good. HEAD is bad. I get
the
following line with release-7.01h.
Links to \hyperref[sec-1]{Heading1}
Jambunathan K
Marvin Doyley writes:
> Org mode is now a part of my daily work-flow, not only do I use it for
> teaching, scheduling my time, but I also use it to store my research
> notes. The only snag is several of my collaborators is tied to
> microsoft word, and thus my only work around is to export my no
Jambunathan K writes:
>> However, what would be ideal would be if there were a tool which would
>> take a Word document with /track changes/ and generate a patch file for
>> a text version of that document... that could then provide some
>> mechanism for getting changes back into an org document
Hi Seb,
I just pushed up a change to epresent so that it should now restore your
original value of org-src-fontify-natively -- assuming that you quit
epresent with the epresent-quit command (bound to "q").
Best -- Eric
Sébastien Vauban writes:
> Hello Eric,
>
> After having run epresent, I got
Hi Seb,
Sébastien Vauban writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a
>> very nice little utility for giving presentations using Emacs as the display
>> engine. Obviously I was aghast to learn that epresent didn't work
Jambunathan K writes:
> "Eric Schulte" writes:
>
>> Hi,
>>
>> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
>> It's a very nice little utility for giving presentations using Emacs as
>> the display engine. Obviously I was aghast to learn that epresent
>> didn't work with O
Łukasz Stelmach writes:
> Richard Riley writes:
>
>> "Eric Schulte" writes:
>>
>>> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
>>> It's a very nice little utility for giving presentations using Emacs as
>>> the display engine.
> [...]
>>> http://github.com/eschulte/epres
Hi Scot,
Scot Becker writes:
> Eric,
>
> This is cool and very useful. Thanks.
>
Thanks, it was fun to work on. Also, most of the cool functionality
already existed in Tom's original version, I just rebased it against
Org-mode.
>
> This must be Zeitgeist-y because I was thinking about prepar
Christopher Allan Webber writes:
>
> However, yeah, I've also been interested in a less nerdy presentation
> route myself... s5? One of these others? There seem to be a lot of
> good options these days. :)
>
and here I've been specifically looking for nerdier presentation options :)
Thomas S. Dye wrote:
> On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote:
>
>
> This is a regression. release-7.01h is good. HEAD is bad. I get the
> following line with release-7.01h.
>
> Links to \hyperref[sec-1]{Heading1}
>
> Jambunathan K.
>
> Aloha Jambunathan
Hi Jambunathan,
On Oct 28, 2010, at 2:40 PM, Jambunathan K wrote:
I have every reason to believe that upcoming version of Org would be
tagged as 7.02. Earlier I had argued that version strings be
version-to-list compatible. I would like to reiterate it.
My real concern is that 7.02 would be d
Scot Becker writes:
> I once saw a video of someone doing a live presentation on something
> Emacs-y and he did the presentation by typing headlines, lists and
> detail in a clean Emacs buffer as he went along, similar to the way
> that some teachers might write out subject headings or outlines o
Eric,
Just retried and was able to get it to work. Perhaps someone should add this
to the ob-doc-latex page? For reference, I tried each of the following:
Works: 1) #+begin_src latex :headers \renewcommand{\rmdefault}{cmss}
Doesn't work: 2) #+begin_src latex :headers
'("\\renewcommand{\rmdefaul
On Tue, Oct 26, 2010 at 6:01 PM, Eric Schulte wrote:
> Hi,
>
> First my previously pasted :exports code will throw errors on
> interactive evaluation (i.e. when not exporting), this alternative
> should be more robust.
>
> :exports (if (and (boundp 'latexp) latexp) "code" "results")
>
> As for pl
On Oct 28, 2010, at 11:01 AM, Jambunathan K wrote:
"Thomas S. Dye" writes:
On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote:
Hi Thomas,
"Thomas S. Dye" wrote:
The manual is silent about what happens to external links on export
to
LaTeX. I'm finding that internal links export to HTML
"Thomas S. Dye" writes:
> On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote:
>
>> Hi Thomas,
>>
>> "Thomas S. Dye" wrote:
>>> The manual is silent about what happens to external links on export
>>> to
>>> LaTeX. I'm finding that internal links export to HTML and work as
>>> expected
>>> there.
On Oct 28, 2010, at 10:18 AM, Sébastien Vauban wrote:
Hi Thomas,
"Thomas S. Dye" wrote:
The manual is silent about what happens to external links on export
to
LaTeX. I'm finding that internal links export to HTML and work as
expected
there. In the pdf file via LaTeX the internal links are
"Eric Schulte" writes:
> Hi,
>
> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
> It's a very nice little utility for giving presentations using Emacs as
> the display engine. Obviously I was aghast to learn that epresent
> didn't work with Org-mode documents. I took the li
Hi Thomas,
"Thomas S. Dye" wrote:
> The manual is silent about what happens to external links on export to
> LaTeX. I'm finding that internal links export to HTML and work as expected
> there. In the pdf file via LaTeX the internal links are colored, but aren't
> active. Is this the expected behav
Peter Frings writes:
> We once thought of having some markup in our LaTeX files to track changes,
> offering annotations. If
> I recall correctly, we had a command \changed{old}{new}{comment}.
> You could leave out the new or old text part: newly added text would be
> \changed{}{bla bla}{this is
>
Eric,
This is cool and very useful. Thanks.
This must be Zeitgeist-y because I was thinking about preparing
presentations in Emacs this week. Then I saw slidy, now this and s5.
Here's a further idea, to see what people think. Do you think it would be
possible to make a temporary org-mode disp
Hello Eric,
After having run epresent, I got this error when trying to publish my
theme-test.org file (sent on this list a couple of days ago -- no reaction
BTW ;-)).
--8<---cut here---start->8---
Debugger entered--Lisp error: (void-function -mode)
-mode()
Aloha all,
The manual is silent about what happens to external links on export to
LaTeX. I'm finding that internal links export to HTML and work as
expected there. In the pdf file via LaTeX the internal links are
colored, but aren't active. Is this the expected behavior or am I
possibl
Samuel Wales writes:
> 2) You are also making tea right now. You want a reminder
> in 5m to drink it.
So true ;-) ICRBIDWT[*]
--
Miłego dnia,
Łukasz Stelmach
[*] I could refrain but I didn't want to ;-)
___
Emacs-orgmode mailing list
Pleas
"Eric Schulte" writes:
> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
> It's a very nice little utility for giving presentations using Emacs as
> the display engine.
[...]
> http://github.com/eschulte/epresent
> (instructions in the README)
I am preparing a talk about org
Hi Eric,
"Eric Schulte" wrote:
> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey. It's a
> very nice little utility for giving presentations using Emacs as the display
> engine. Obviously I was aghast to learn that epresent didn't work with
> Org-mode documents. I took the liber
Richard Riley writes:
> "Eric Schulte" writes:
>
>> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
>> It's a very nice little utility for giving presentations using Emacs as
>> the display engine.
[...]
>> http://github.com/eschulte/epresent
>> (instructions in the README)
>
Sébastien Vauban
writes:
> Hello,
>
> Here is a minimal example for comments about the agenda filtering applied on
> the clock report of logged activities.
>
> * Work :work:
> :PROPERTIES:
> :CATEGORY: Work
> :END:
>
> ** Cli
Bastien
> Can you suggest a new default for `version-regexp-alist' so that
> 7.01 is considered older than 7.10?
I assume there is a typo here. Just for the sake of clarification:
(version-list-= (version-to-list "7.01") (version-to-list "7.1")) is t
(version-list-< (version-to-list "7.01") (ve
"Eric Schulte" writes:
> Hi,
>
> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
> It's a very nice little utility for giving presentations using Emacs as
> the display engine. Obviously I was aghast to learn that epresent
> didn't work with Org-mode documents. I took the li
Signed-off-by: Julien Danjou
---
ORGWEBPAGE/Changes.org |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/ORGWEBPAGE/Changes.org b/ORGWEBPAGE/Changes.org
index 549aed4..9a6b934 100644
--- a/ORGWEBPAGE/Changes.org
+++ b/ORGWEBPAGE/Changes.org
@@ -374,7 +374,7 @@ on Worg.
I should point out that this is more a matter of getting the ideas
posted than a feature request.
On 2010-10-28, Samuel Wales wrote:
> I wrote this a while back, and now I see that the manual
> describes a countdown timer. So now might be a good
> time.
>
> ===
>
> We've discussed something like
Hello Bastien
Bastien writes:
> Jambunathan K writes:
>
>> I have every reason to believe that upcoming version of Org would be
>> tagged as 7.02. Earlier I had argued that version strings be
>> version-to-list compatible. I would like to reiterate it.
>>
>> My real concern is that 7.02 would
I wrote this a while back, and now I see that the manual
describes a countdown timer. So now might be a good
time.
===
We've discussed something like this before, but it seems
there have been changes, so I am starting from scratch.
Wondering how much of the functionality exists in Emacs or
Org.
On Oct 27, 2010, at 11:12 PM, Carsten Dominik wrote:
On Oct 28, 2010, at 2:08 AM, Thomas S. Dye wrote:
Aloha all,
This might be wildly impractical for most of you, but I'd be happy
to facilitate an Org-mode conference at Keauhou Beach Resort in
Kona, Hawaii. I organized a conference th
Since we're talking about meet-ups, I'd like to say it would be great to
see an informal org-mode meet-up attached to other conferences one might
attend.
Not as an alternative to the Hawaii proposal, but as an "also."
cheers,
r
___
Emacs-orgmode mailin
On Oct 28, 2010, at 1:10 AM, Dan Davison wrote:
"Thomas S. Dye" writes:
On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
"Thomas S. Dye" writes:
Hi Dan,
Glad to know that Darlan's slowdown is fixed.
No change here that I can tell. Now that I've had org-src-fontify-
natively set to t f
#+TITLE: Installation Notes for an app
#+LANGUAGE: en_US
* Global constants
** Development
#+tblname: dev-params
| serverName | host1|
| appBaseDir | /cygdrive/d/dir1 |
** Staging
#+tblname: stg-params
| serverName | host2|
| appBaseDir | /cygdrive/d/dir2 |
** Pro
Hi Ezequiel,
Ezequiel Birman writes:
> Thanks, it works now though I am not sure about the best way to load
> emacs. Nowadays I use 'emacsclient -c' and let it handle the process of
> starting the daemon but
>
> 1. Should I let org-interaction.el start the server from now on?
>(eg. by loadin
"Eric Schulte" writes:
> Hi,
>
> Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
> It's a very nice little utility for giving presentations using Emacs as
> the display engine. Obviously I was aghast to learn that epresent
> didn't work with Org-mode documents. I took the li
Hi,
Phil Hagelberg recently introduced me to epresent.el by Tom Tromey.
It's a very nice little utility for giving presentations using Emacs as
the display engine. Obviously I was aghast to learn that epresent
didn't work with Org-mode documents. I took the liberty of reworking it
so that it run
Hello,
In page http://orgmode.org/guide/Working-With-Source-Code.html,
see "further reading": link "chapter 14" broken (recursive, BTW?).
Best regards,
Seb
--
Sébastien Vauban
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies t
Jambunathan K writes:
> I have every reason to believe that upcoming version of Org would be
> tagged as 7.02. Earlier I had argued that version strings be
> version-to-list compatible. I would like to reiterate it.
>
> My real concern is that 7.02 would be deemed as equivalent to 7.2
> internall
Patch 347 (http://patchwork.newartisans.com/patch/347/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C4CC94AAB.2030908%40easy-emacs.de%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-
Jambunathan K writes:
> Jules Bean writes:
>
>>>
>>> Hi Tom,
>>>
>>> I've used fontification in Org code blocks constantly for a couple of
>>> months now, and I do not agree that there are any editing or unfolding
>>> delays which should deter typical Org users from using fontified src
>>> blo
Jules Bean writes:
>>
>> Hi Tom,
>>
>> I've used fontification in Org code blocks constantly for a couple of
>> months now, and I do not agree that there are any editing or unfolding
>> delays which should deter typical Org users from using fontified src
>> blocks. In typical usage I do not exp
I have every reason to believe that upcoming version of Org would be
tagged as 7.02. Earlier I had argued that version strings be
version-to-list compatible. I would like to reiterate it.
My real concern is that 7.02 would be deemed as equivalent to 7.2
internally by the versioning subsystem and
Noorul Islam noorul.com> writes:
>
> On Wed, Oct 27, 2010 at 4:13 PM, Axis gmx.ch> wrote:
> > Hello,
> >
> > I'm having a struggle capturing a plain text item under a headline; it
> > always gets added to the bottom of the file. List items or org entries can
> > be stowed away properly without
>
> Hi Tom,
>
> I've used fontification in Org code blocks constantly for a couple of
> months now, and I do not agree that there are any editing or unfolding
> delays which should deter typical Org users from using fontified src
> blocks. In typical usage I do not experience any delays whatsoeve
Jambunathan K writes:
> Eric S Fraga writes:
>> I'm not sure I understand. change tracking in org is trivial (git,
>> mercurial, etc); it's extracting Word change tracking information in a
>> form usable by other tools that is not trivial...
>
> My intention was really to bring attention to the
Eric S Fraga writes:
> Jambunathan K writes:
>
>> Eric
>>
>>> However, what would be ideal would be if there were a tool which would
>>> take a Word document with /track changes/ and generate a patch file for
>>> a text version of that document... that could then provide some
>>> mechanism for
"Thomas S. Dye" writes:
> On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
>
>> "Thomas S. Dye" writes:
>>
>>> Hi Dan,
>>>
>>> Glad to know that Darlan's slowdown is fixed.
>>>
>>> No change here that I can tell. Now that I've had org-src-fontify-
>>> natively set to t for a while, I can see tha
Hello,
Wanting to use Babel as much as possible, writing a lot of scripts that I
tangle (and eventually share with others), I find that prefixing all tangled
files shoud be a good habit in order to directly see which files (in dired)
are the results of a tangling process.
Of course, I can have th
On 28 Oct 2010, at 11:15, Scot Becker wrote:
> Jambunathan,
>
> (2) could be useful but a bit far-fetched at the
> moment.
>
> Really? Lots of us track changes with git, sometimes by means of one of the
> Emacs interfaces for it like Magit. You may be thinking of some
> interface-level fea
Jambunathan K writes:
> Eric
>
>> However, what would be ideal would be if there were a tool which would
>> take a Word document with /track changes/ and generate a patch file for
>> a text version of that document... that could then provide some
>> mechanism for getting changes back into an org
diff --git a/doc/org.texi b/doc/org.texi
index 54f52e2..7630830 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1708,8 +1708,7 @@ unpredictable for you, configure the variables
@table @kbd
@tsubheading{Creation and conversion}
-...@kindex C-c |
-...@item C-c |
+...@orgcmd{c-c |,org-table-crea
Am 28.10.2010 11:45, schrieb Andreas Röhler:
___
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
Sorry, just seeing an error inside. Please don'
diff --git a/doc/org.texi b/doc/org.texi
index 54f52e2..7630830 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1708,8 +1708,7 @@ unpredictable for you, configure the variables
@table @kbd
@tsubheading{Creation and conversion}
-...@kindex C-c |
-...@item C-c |
+...@orgcmd{c-c |,org-table-crea
Jambunathan,
(2) could be useful but a bit far-fetched at the
> moment.
>
Really? Lots of us track changes with git, sometimes by means of one of the
Emacs interfaces for it like Magit. You may be thinking of some
interface-level features which aren't available by this method, like the
ability
On Oct 28, 2010, at 2:08 AM, Thomas S. Dye wrote:
Aloha all,
This might be wildly impractical for most of you, but I'd be happy
to facilitate an Org-mode conference at Keauhou Beach Resort in
Kona, Hawaii. I organized a conference there for 150 archaeologists
a few years ago and the fac
Thanks for giving me an excuse to visit Hawaii! Actually, it would be
a tough sell to me wife, if you can believe that!
Jeff
On Wed, Oct 27, 2010 at 8:08 PM, Thomas S. Dye wrote:
> Aloha all,
>
> This might be wildly impractical for most of you, but I'd be happy to
> facilitate an Org-mode confe
> I added a link to the Feedback section and another to ESR "How To Ask
> Questions The Smart Way" on the index page of http://orgmode.org
>
> Thanks everyone!
Thank you for sharing, Bastien. I had never read that essay before.
And it's exactly where I would expect to find it.
Best,
Jeff
--
Jef
Eric
> However, what would be ideal would be if there were a tool which would
> take a Word document with /track changes/ and generate a patch file for
> a text version of that document... that could then provide some
> mechanism for getting changes back into an org document (modulo problems
> w
Hi Anthony
Anthony Lander writes:
> Is the unfamiliar idiom the backtick list with the ,variables in it,
> by chance?
No it was more stuff like `return' and `return-from'.
> Ah, sorry. This I should have documented. The problem is that TJ3
> fails to compile the file if there is a leaf node wi
Marvin Doyley writes:
> This is indeed a unique way of looking at the problem. I am not sure
> converting from word to Org is
> the way to go, because vast majority of my research notes are already
> in Org. But having said that a
> good work around could be to create a crude version in word (dit
New patch fixing these issues is attached.
Let me know of any other problems.
On Tue, Oct 26, 2010 at 1:23 AM, Carsten Dominik
wrote:
>
> On Oct 26, 2010, at 10:21 AM, Nicolas Goaziou wrote:
>
>> Hello,
>>
>>> Nathaniel Flath writes:
>>
>>> I think I've fixed the issues brought up with this
Bruno Tavernier writes:
> I search on Worg and in the info file but could not find if there is
> an option to select the position (left,center,right) of beamer's
> frametitle and block?
I cannot help you with the block problem but I would suggest that the
frametitle formatting is the responsibil
Am 27.10.2010 20:11, schrieb Bastien:
Andreas Röhler writes:
BTW, is somewhere documented, how to load the devel-tree from emacs -Q?
Assuming your devel-tree is in ~/install/git/org-mode/ you need to do
a (require 'org) so that the devel version replaces the one loaded by
Emacs.
Thanks,
84 matches
Mail list logo
