getting out of sync is possible even with non-buggy code. i wonder if
it would make sense to do a quick and dirty comparison of the headline
to error if it is different?
feel free to disregard if this is not a good idea.
Fletcher Charest writes:
> Nick, you say you could not reproduce the bug using version
> 8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g798bb8d. Just
> out of curiosity: does the '888' in '8.2.5h-888-g798bb8d' is a number
> that is incremented chronologically? If this is correct (I'm no
Hi List,
I wrote a little library that is just a small toolbox, but quite useful
in combination with outshine.el and outorg.el.
This was mainly inspired by the new announcement of the new ox-gfm.el
exporter, because it enables the export of nice looking README.md files
for github from Org-mode
Hi list,
I've just found a bug in `org-test-with-temp-text' and have fixed it. Please
find attached my patch for the fix. Here's the description from git commit
message:
According to the docstring, if the string "" appears in TEXT then the
string "" is removed and point is placed there. The probl
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> This minimal Org buffer "tmp<2>"
>>
>> ,
>> | #+OPTIONS: prop:t
>> |
>> | * A
>> | :PROPERTIES:
>> | :EXPORT_OPTIONS: prop:nil
>> | :END:
>> |
>> | C
>> |
>> | * B
>> | :PROPERTIES:
>> | :D
Hello,
Thorsten Jolitz writes:
> This minimal Org buffer "tmp<2>"
>
> ,
> | #+OPTIONS: prop:t
> |
> | * A
> | :PROPERTIES:
> | :EXPORT_OPTIONS: prop:nil
> | :END:
> |
> | C
> |
> | * B
> | :PROPERTIES:
> | :DESCRIPTION: Headline B
> | :END:
> |
> | D
>
Hello,
Thorsten Jolitz writes:
> when I export this org buffer
>
> ,---
> | * A
> |
> | ** A1
> |
> | text
> |
> | * B
> |
> | ** B1
> |
> | more text
> |
> | * C
> |
> | ** C1
> |
> | even more text
> `---
>
> to another org buffer I get:
>
> ,--
Hi List,
when I export this org buffer
,---
| * A
|
| ** A1
|
| text
|
| * B
|
| ** B1
|
| more text
|
| * C
|
| ** C1
|
| even more text
`---
to another org buffer I get:
,-
| # Created 2014-04-09 Mi 23:04
| #+TITLE: tmp<3>
| #
Hi List,
This minimal Org buffer "tmp<2>"
,
| #+OPTIONS: prop:t
|
| * A
| :PROPERTIES:
| :EXPORT_OPTIONS: prop:nil
| :END:
|
| C
|
| * B
| :PROPERTIES:
| :DESCRIPTION: Headline B
| :END:
|
| D
`
exports to
,--
Rob Stewart writes:
>
> I asked the question below a few days ago, about whether
> `org-preview-latex-fragment` is sensitive document class options that
> might affect alignment. I've so far not received feedback, and
> wondered whether there is more information that I could provide, or if
> my q
Hi,
I asked the question below a few days ago, about whether
`org-preview-latex-fragment` is sensitive document class options that
might affect alignment. I've so far not received feedback, and
wondered whether there is more information that I could provide, or if
my question is not interesting to
Dear list,
Following all the nice comments you made after my first announce, I just
uploaded an updated version of the org-capture extension.
You can find it on the main webpage
http://chadok.info/firefox-org-capture/ or on the Mozilla addons
repository https://addons.mozilla.org/fr/firefox/addon
Glenn Morris writes:
> Glenn Morris wrote:
>
>> Perhaps this is fixed now, according to comments at:
>>
>> http://lists.gnu.org/archive/html/emacs-orgmode/2014-03/msg01176.html
>>
>> (It would be great if someone would keep an eye on these Org bugs that
>> get reported to Emacs and update them wh
Nick, you say you could not reproduce the bug using version
8.2.5h-667-g971dc4, but you did with version 8.2.5h-888-g798bb8d. Just out
of curiosity: does the '888' in '8.2.5h-888-g798bb8d' is a number that is
incremented chronologically? If this is correct (I'm not familiar with this
at all), FWIW,
Nick Dokos writes:
>
> Starting from release_8.2.5h-888-g798bb8d (this was latest as of this
> morning) and reverting the above commit fixes Fletcher's problem.
>
Just to be clear: I'm *not* advocating that the commit be reverted.
I used the revert just to confirm that something in that patch ca
I'm using org-mode 8.2.
I'm trying to use clocking all the time during my working day to know later, what I used my time for.
Unfortunately, I often forget clocking in and therefore have clocking gaps in my files.
I can visualize them with the "vc" command in the agenda view, but now I have t
On Wednesday, 9 Apr 2014 at 09:04, David Belohrad wrote:
> Hi,
>
> it has been some time I've switched to org for all my life agenda. I
> have to say that it is a perfect tool and I cannot imagine my life
> without it any more.
I just tried to imagine this. I cannot even remember the whole set
Charles Berry writes:
> Lars Tveito student.matnat.uio.no> writes:
>
>>
>> Hi, thanks for checking it out!
>>
>> Thorsten Jolitz writes:
>>
>> > Thorsten Jolitz gmail.com> writes:
>> >
>> >> Lars Tveito student.matnat.uio.no> writes:
>> >>
>> >>> Hi!
>> >>>
>> >>> I have written an exporter
Hi,
it has been some time I've switched to org for all my life agenda. I
have to say that it is a perfect tool and I cannot imagine my life
without it any more. Thanks for all this excellent sw, I guess we all
know how much effort one has to invest into the software development to
make it ergonom
Hello,
Am 08.04.2014 21:31, schrieb Nicolas Goaziou:
n...@tsdye.com (Thomas S. Dye) writes:
When I was working on the project I hoped the Org mode developers would
choose to "eat their own dog food" (as Carsten put it to me) and prepare
the texinfo and other documentation with Org mode source.
Lars Tveito writes:
> Hi, thanks for checking it out!
> Getting it to work with source-blocks was the feature I missed the most
> from the vanilla markdown exporter. If you specify a language in the
> source-block it will be added to the exported version as well; a problem
> occurs if you specify
21 matches
Mail list logo