Nick Dokos ndo...@gmail.com writes:
Brian Callies br...@gibbous.org writes:
I'm sure I must be doing something obviously wrong, but I've had no
success at publishing a project I've just created. I've been working
on this error for some time, incidentally fixing other mistakes, but
I'm
Hi Malcom,
2013ko uztailak 17an, malcolm cook-ek idatzi zuen:
Hi,
I am creating .svg files with R source blocks and ESS in org.
I am happily viewing them in-line in my emacs buffer.
I am happily exporting as html and viewing them in-line in the resulting web
page, including a
At Fri, 26 Jul 2013 12:20:37 +0200,
Nicolas Goaziou wrote:
David Maus dm...@ictsoc.de writes:
Thanks for your answer. It seems I got confused with the current state
of URI-encoding. Please scratch my previous suggestion and let's start
over.
The more I think about it the more I grow
David Maus dm...@ictsoc.de writes:
The more I think about it the more I grow certain that it is NOT about
URI encoding but protecting a string.
This is what I mean.
`[' and `]' are not forbidden per se, they belong to the set of
reserved characters (see RFC 3986, 2.2.).
characters in the
Just wondering if there's a better way to handle LaTeX commands written inline,
when the command arguments span a line break. Currently, LaTeX export preserves
curly braces as is if a pair of them is on a single line, but it escapes them
if there's a line break in between:
~~ org
Sections may
On 07/27/2013 01:21 AM, Nick Dokos wrote:
Nick Dokos ndo...@gmail.com writes:
This was valid for org 7.x, but for org 8.x you have to say
:publishing-function org-html-publish-to-html
BTW, you should check your installation: presumably you are not getting
on error when calling
Sebastien Vauban sva-n...@mygooglest.com writes:
Matt Price wrote:
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
After finding that =fill-paragraph= has regressed again, I threw
together a quick hack to allow for creating unit tests in orgmode. The
result is at [1].
This simply lets you create an org file like so:
#+BEGIN_SRC org
,* Test heading
,#+BEGIN_SRC emacs-lisp
(org-test-def
Hello,
James Harkins jamshar...@gmail.com writes:
Just wondering if there's a better way to handle LaTeX commands
written inline, when the command arguments span a line break.
Currently, LaTeX export preserves curly braces as is if a pair of them
is on a single line, but it escapes them if
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 email comments no longer works.
To test, launch =emacs -Q= and create a buffer with
#+BEGIN_EXAMPLE
The
cat
in
the
hat
Nicolas Goaziou n.goaz...@gmail.com wrote:
Daniel Hackney d...@haxney.org writes:
After finding that =fill-paragraph= has regressed again,
Would you mind elaborating on that? I could have overlooked the problem.
I just started a separate thread about it.
--
Daniel Hackney
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
-Brian
On 07/26/2013 08:33 PM, Nick Dokos wrote:
Brian Callies
Hello,
Daniel Hackney d...@haxney.org writes:
After finding that =fill-paragraph= has regressed again,
Would you mind elaborating on that? I could have overlooked the problem.
Regards,
--
Nicolas Goaziou
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 email comments no longer works.
It has been discussed on this ML already. Org mode is
Toke Høiland-Jørgensen t...@toke.dk writes:
Michael Brand michael.ch.br...@gmail.com writes:
When implementing this, consider also whether the END_DATE should be
an agenda entry on its own and of which kind, warning period etc. I
tried to make an example that shows this issue.
Adding to
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 email comments no longer works.
It has been
Hi Arne,
I also don't use the output format that includes days.
Try setting the following variable:
(setq org-time-clocksum-format
'(:hours %d :require-hours t :minutes :%02d :require-minutes t))
Regards,
Bernt
Arne Babenhauserheide arne_...@web.de writes:
Remember to cover the
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 email comments no longer works.
Maybe we
Thanks for the info. I took it up as a challenge to finally learn a
little elisp. This is what I have so far, which appears to work as long
as I expand the entire subtree to be exported. I'd appreciate any
criticism since I really don't know if I'm handling things the best
possible way.
(defun
It appears that I'm using the properties syntax correctly, however I
cannot seem to get export to use the options I set in the properties
drawer. If I move the LaTeX_CLASS and OPTIONS over to their #+
equivalents at the top of the file they work just fine. Is there
something (hopefully not *too*
20 matches
Mail list logo
