Rasmus writes:
> Sorry; you posted a code first which didn't work at all for me; I
> tried to fix it, and I posted a code which I though worked but in the
> end it didn't. Thus, I though it would be fair to post another
> message stating this, if nothing else than for future viewers.
I meant: w
t...@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou writes:
>> That's a bit of work, because, so far, node-property values are not
>> parsed. So it would require to define a new class of node-properties:
>> those with a parsed value. But then, how to decide which properties have
>> their va
Nicolas Goaziou writes:
> Philipp Kroos writes:
>
>> That said, I'm fine with the situation, but I'ld suggest a note in the
>> documentation that makes this limitation to subtree-exports clear (and
>> possibly points out the workarounds). What do you think?
>
> Sure. What should be written in th
Nicolas,
Thanks for your reply.
> I meant: what is the exact problem with my code (with examples and
> expected output if possible)? It shouldn't be hard to fix.
They are not caught by the regexp. And I wasn't able to find a regexp
which could correctly identify all cases. I have a sample in
Rasmus writes:
>> I meant: what is the exact problem with my code (with examples and
>> expected output if possible)? It shouldn't be hard to fix.
>
> They are not caught by the regexp. And I wasn't able to find a regexp
> which could correctly identify all cases. I have a sample in the
> footn
Nicolas,
> That's because you use "booktabs" by default. It creates horizontal
> rules, and the filter hence doesn't apply.
Aha. Is this (again) a misunderstanding because I though of org
source? I tried to identify org tables with rules.
> Since e-latex back-end doesn't strip anything in reg
Hi,
Would it be desirable if the new exporter took the variable
org-export-date-timestamp-format into consideration when formatting
dates? Or is there another way of dealing with the formatting of
dates?
┏━━━┫ org-export-date-timestamp-format ~"%Y-%m-%d"~ ┃
┃ Type: string
┃ Since: Emacs
The following changes since commit c2223c8979c5510e01c0dd6cc2378b71484828fc:
still execute code block even if :results none (2012-11-17 17:54:08 -0700)
are available in the git repository at:
git://git.baby-gnu.net/org-mode tags/fix-and-test-org-exp-inclusion
for you to fetch changes up to
On Sat, Nov 17, 2012 at 6:25 PM, Manish wrote:
[snip (21 lines)]
>
> =F12 SPC= with =V= is so much better at doing project reviews than
> anything else I have ever seen. My only gripe is that functions called
> by =V= and =P= do not refresh the agenda. I am trying to understand
> enough elisp to
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>
>>> That's a bit of work, because, so far, node-property values are not
>>> parsed. So it would require to define a new class of node-properties:
>>> those with a parsed value. But then, how to decide
Aloha all,
I have this in the Org file:
@@info:@email{emacs-orgmode@@gnu.org}@@
I expect to get this in the texi file:
@email{emacs-orgmode@@gnu.org}
Instead, I get this:
@email{emacs-orgmodegnu.org@}
In general, the export snippets work very well. I think this might be a
corner case ca
Hello Tom,
On Nov 18, 2012 1:29 PM, "Thomas S. Dye" wrote:
>
> Aloha all,
>
> I have this in the Org file:
>
> @@info:@email{emacs-orgmode@@gnu.org}@@
>
> I expect to get this in the texi file:
>
> @email{emacs-orgmode@@gnu.org}
>
> Instead, I get this:
>
> @email{emacs-orgmodegnu.org@}
>
Th
Aloha Jon,
Jonathan Leech-Pepin writes:
> Hello Tom,
>
> On Nov 18, 2012 1:29 PM, "Thomas S. Dye" wrote:
>>
>> Aloha all,
>>
>> I have this in the Org file:
>>
>> @@info:@email{emacs-orgmode@@gnu.org}@@
>>
>> I expect to get this in the texi file:
>>
>> @email{emacs-orgmode@@gnu.org}
>>
>> Inst
Rasmus writes:
>> Then the backend can add the alignment as an optional argument in math
>> mode only when the name of the environment ends with a star and the
>> alignment string is one character long.
>
> In the LATEX_ATTR or as in the example above? The former I assume.
Correct.
>> To circu
Aaron Ecay writes:
> 2012ko azaroak 17an, Eric Schulte-ek idatzi zuen:
>
>> Oh!, thanks for catching this, I just pushed up a fix.
>
> This is no longer a (complete) fix for the original problem, though. (A
> large part of) the slowdown comes from reading the results from a temp
> file and trans
Hi,
I just want to let you know that org-mode (org-20121112 from package.el) is
working well with yasnippets 0.8.0 (beta)
with following configuration:
(defun yas-org-very-safe-expand ()
(let ((yas-fallback-behavior 'return-nil))
(and (fboundp 'yas-expand) (yas-expand
(add-hook 'org-mo
Eric Schulte writes:
> Aaron Ecay writes:
>
>> 2012ko azaroak 17an, Eric Schulte-ek idatzi zuen:
>>
>>> Oh!, thanks for catching this, I just pushed up a fix.
>>
>> This is no longer a (complete) fix for the original problem, though. (A
>> large part of) the slowdown comes from reading the resu
Hi,
AFAIK, if the markup syntax (=code=, *bold*, ..) is directly followed
by non-whitespace characters, then it will not be marked-up:
=hello=there
/not/italic
This may be right decision on English text, but in some languages, the
postposition (grammar) will be postfixed without spaces in
Hello,
** cin...@gmail.com [2012-11-19 14:32:21 +0900]:
> Hi,
> AFAIK, if the markup syntax (=code=, *bold*, ..) is directly followed
> by non-whitespace characters, then it will not be marked-up:
>=hello=there
>/not/italic
> This may be right decision on English text, but in some langu
When the new exporter produces a TeX file that contains unicode characters,
Emacs tries to save this file with coding systems `undecided-unix´ and
`iso-latin1-unix´, both of which don't work of course (and the latter would
likely be wrong for some characters). While it should be possible to change
20 matches
Mail list logo
