Daniel Hackney d...@haxney.org writes:
Nicolas Goaziou n.goaz...@gmail.com wrote:
Daniel Hackney d...@haxney.org writes:
I proposed a fix [1] for this back in 2010, but it seems to have regressed
again. `org-fill-paragraph' no longer makes use of a `fill-prefix', so
filling things like
Hi,
sorry the patch was incomplete. The correct one is on a branch I just
pushed named tz-test.
For me it works the same but maybe it works for you.
Cheers,
Simon
On 07/23/2013 04:42 PM, Stephen Eglen wrote:
Yes, org-mode does not recognize the [UTC], that is just a helper for
exactly
Hi,
I am working on the org-reveal exporter and I need to convert a string
get from org-element-property into HTML format. The property string have
some Org-mode markups that need to be converted to relevant HTML labels.
For example, a string of /italic/ to iitalic/i
Is there any existing
On 07/28/2013 12:18 PM, Yujie Wen wrote:
Hi,
I am working on the org-reveal exporter and I need to convert a string
get from org-element-property into HTML format. The property string have
some Org-mode markups that need to be converted to relevant HTML labels.
For example, a string of
Hello,
Yujie Wen yjwen...@gmail.com writes:
I am working on the org-reveal exporter and I need to convert a string
get from org-element-property into HTML format. The property string have
some Org-mode markups that need to be converted to relevant HTML labels.
For example, a string of
At Sun, 28 Jul 2013 14:06:54 +0530,
Jambunathan K wrote:
If Org links are escaped by Org will the URLs be functional outside of
Org?
i.e., If I am on some machine, that has no Emacs or Org or if I am using
a version of Org that uses new unescape algorithm but the original
link was
Hello,
Jambunathan K kjambunat...@gmail.com writes:
If Org links are escaped by Org will the URLs be functional outside of
Org?
If there is an unencoding part, and if that part cannot happen for
some reason, links will be unusable outside Org.
That's already the case with the current
Yujie Wen yjwen...@gmail.com writes:
Hi,
I am working on the org-reveal exporter and I need to convert a
string get from org-element-property into HTML format. The property
string have some Org-mode markups that need to be converted to
relevant HTML labels. For example, a string of
Hi, Robert, Nicolas and Eric,
Thanks to all of you for the kind answers. org-export-data-with-backend
and org-element-parse-secondary-string best meet my requirements. They
worked just as I expected. Thanks again.
Regards,
Yujie
2013/7/28 Eric Abrahamsen e...@ericabrahamsen.net
Yujie Wen
Brian Callies br...@gibbous.org writes:
Thank you. I thought it was probably something like this.
Is there updated documentation yet for 8.x?
The Worg link below is one site I based my attempt on:
http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html
The manual is updated,
Good day!
I'm running emacs-23.3.1 on an up-to-date Xubuntu 12.04.2 system.
It includes orgmode-6.33x.
I downloaded orgmode-8.0.6, but the build failed with these error
messages:
0make
Description: Binary data
The messages suggest that 8.0.6 is not compatible with my version of Emacs.
Hello,
Kenneth Jacker k...@be.cs.appstate.edu writes:
I downloaded orgmode-8.0.6, but the build failed with these error
messages:
[...]
The messages suggest that 8.0.6 is not compatible with my version of
Emacs.
Org will try to be compatible with Emacs 23 at least until Emacs 25
release.
On Fri, Jul 26, 2013 at 06:54:08PM -0600, Eric Schulte wrote:
Rick Frankel r...@rickster.com writes:
The later is not valid call line syntax, see [1] for a full description
of the call line syntax. In effect what happens in the latter case, is
you set :colnames to yes].
Oh, ok. I just saw
jk I was rude, sorry. I C-s ed for error and landed up in makeinfo.
jk
jk The messages pertaining to scroll etc usually pop up as warning
jk messages in Emacs-24. This is routine. I didn't anticipate the
jk functions were not defined on Emacs 23 so I just overlooked them.
No problem
The messages suggest that 8.0.6 is not compatible with my version of
Emacs.
ng Org will try to be compatible with Emacs 23 at least until Emacs
ng 25 release. I fixed the compilation errors. They should be gone in
ng Org 8.0.7.
Excellent!
How did you get around the missing Emacs
Hello,
as title states, commit '3142297d69f6063221215757a3ba9c74adcf3e43'
breaks one of my Org document (I have many but faced with a bug only
with particular one). In that file tables contain data (three columns,
one header) which are transformed and tangle to files (xml, txt). Before
the commit
Eric Schulte writes:
I've just pushed up that patch.
…which breaks testing:
10 unexpected results:
FAILED ob-exp/use-case-of-reading-entry-properties
FAILED test-ob-header-arg-defaults/global/call
FAILED test-ob-header-arg-defaults/global/noweb
FAILED
17 matches
Mail list logo
