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* ob
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 ewd
Nicolas Goaziou wrote:
> Daniel Hackney 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 can introduce some support
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 writes:
> Remember to cover the basics, that is,
Nicolas Goaziou writes:
> I think it would be less ambiguous to use ICALENDAR_UNTIL (or UNTIL),
> and apply RFC 5545:
Ah, that specifies it nicely, thanks (and that was what I was (trying
to) do with the patch). That would mean exporting the time as well as
the date for end times (and calling th
Nicolas Goaziou wrote:
> Daniel Hackney 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 alr
Toke Høiland-Jørgensen writes:
> Michael Brand 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 this, as mentioned previously,
Daniel Hackney 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 not Message mod
Hello,
Daniel Hackney writes:
> After finding that =fill-paragraph= has regressed again,
Would you mind elaborating on that? I could have overlooked the problem.
Regards,
--
Nicolas Goaziou
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 wri
Nicolas Goaziou wrote:
> Daniel Hackney 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
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
#+
Hello,
James Harkins 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 there's a line bre
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 org-test-fil
"Sebastien Vauban" 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 people, the
On 07/27/2013 01:21 AM, Nick Dokos wrote:
Nick Dokos 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 org-publish-org-to-ht
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 b
David Maus 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 reserved
At Fri, 26 Jul 2013 12:20:37 +0200,
Nicolas Goaziou wrote:
>
> David Maus 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 certain that it
19 matches
Mail list logo
