Hi Thorsten,
Thorsten Jolitz wrote:
> using 'M-: (org-table-convert-region beg end 2) on this output (with
> beg/end being the points before and after the tabular data)
>
> ,---
> | === Error on training data ===
> |
> | Correctly Cla
Hello,
Avery Chan writes:
> After some futzing with the source org file, it's clear that having a
> "_TEXT_ "(where '_' denotes an underline), is incompatible with
> the md-export parser. Upon removing the offending token, the
> md-exporter works as expected.
It should be fixed in maint. Tha
"Sebastien Vauban"
writes:
Hi Sebastien,
[...]
>> From the comment-string:
>>
>> ,---
>> | (org-table-convert-region BEG0 END0 &optional SEPARATOR)
>> |
>> | Convert region to a table.[...]
>> | SEPARATOR specifies the field sep
Thorsten,
Thorsten Jolitz wrote:
> "Sebastien Vauban" writes:
>>>
>>> ,---
>>> | (org-table-convert-region BEG0 END0 &optional SEPARATOR)
>>> |
>>> | Convert region to a table.[...]
>>> | SEPARATOR specifies the field separator i
"Sebastien Vauban"
writes:
> I've considered the following table:
>
> test a b c
> test a b c
> test a b c
> testabc
> test a b c
> test a b c
>
> and tried to convert it with various configs:
>
> - M-x org-table-convert-region
> - C-u M-x org-table
* lisp/org.el (org-time-clocksum-use-effort-durations): Remove
variable.
(org-minutes-to-clocksum-string): Remove references.
* lisp/org-clock.el (org-clocktable-write-default): Remove
references.
We would like the following identity to hold:
(= (org-duration-string-to-minutes "3d 2h")
Thorsten Jolitz writes:
> Yes, I can confirm this. So either (interactive "rP") isn't a valid
> combination, then its a bug in the org command3, or it is a valid
> combination and should work - then its a bug in Emacs 24?
Its a bug in 'org-table-convert-region'.
"PATCH":
replace
,---
Hi Tristan,
this feature request seems simple to implement on one side. However, it
opens a question how to deal with those in general.
\ruby{東} is a very specific command of the CJK package.
If this get's implemented in the standard html exporter, other very special
commands might need to follow.
* Matt Lundin wrote:
> Karl Voit writes:
>
>> However, with the following event, I only get one time stamp onto my
>> agenda (namely the first one of the very same day):
>>
>> ,[ time stamp on the same day ]
>> | ** Event B
>> |
>> | - <2013-05-27 Mon 09:00-12:00>
>> | - <2013-05-27 Mon 13:00
Hi!
I could not find anything yet which says that it's possible (or not)
to define a file variable which enables PROPERTY drawers to be
expanded (only in this current file).
My use case: I usually never store major meta-data in drawers. So I
like the default behavior with closed property drawers.
Karl Voit writes:
> Hi!
>
> I could not find anything yet which says that it's possible (or not)
> to define a file variable which enables PROPERTY drawers to be
> expanded (only in this current file).
>
> My use case: I usually never store major meta-data in drawers. So I
> like the default beha
Karl Voit writes:
> Hi!
>
> I could not find anything yet which says that it's possible (or not)
> to define a file variable which enables PROPERTY drawers to be
> expanded (only in this current file).
>
> My use case: I usually never store major meta-data in drawers. So I
> like the default beha
Thorsten Jolitz writes:
> Karl Voit writes:
>
>> Hi!
>>
>> I could not find anything yet which says that it's possible (or not)
>> to define a file variable which enables PROPERTY drawers to be
>> expanded (only in this current file).
>>
>> My use case: I usually never store major meta-data in d
On Tue, May 28, 2013 at 03:00:40PM +0200, Torsten Wagner wrote:
>
> However, I believe that for many users, the special cases are not very
> frequent and complex. Might it be possible to create a very simple syntax
> for exporting rules which could be either in those above modules or
> directly wi
Dear list,
would someone help me, being not a programmer, to achieve this:
I get Emails, copy them into an org-file and would like to write down comments
on single sentences or paragraphs of the text.
I'd like to mark some text in the copied text of the Email inside the org-file
and get "#+BEG
On Tue, May 28, 2013 at 05:01:56PM +0200, Suvayu Ali wrote:
>
> PS: Actually on second thought it is probably possible to handle this
> with filters although I failed to find the appropriate filter.
>
> So you could try:
>
> #+MACRO: ruby <$1><$2>
>
> And the filter can transl
Suvayu Ali writes:
> On Tue, May 28, 2013 at 03:00:40PM +0200, Torsten Wagner wrote:
>>
>> However, I believe that for many users, the special cases are not very
>> frequent and complex. Might it be possible to create a very simple syntax
>> for exporting rules which could be either in those abo
Hi Torsten,
Thanks for the input,
To have definable export rules would indeed be great, to increase
flexibility while keeping the base exporter simple and lightweight.
I agree that this is somewhat specific, however, I believe that
globally, this is not unfrequent, and will become quite frequent
AW writes:
> Dear list,
>
> would someone help me, being not a programmer, to achieve this:
>
> I get Emails, copy them into an org-file and would like to write down
> comments
> on single sentences or paragraphs of the text.
>
> I'd like to mark some text in the copied text of the Email inside
Thorsten Jolitz writes:
PS
There was one wrong paren, better use this one instead:
,---
| (defun org-wrap-region-in-quote-block ()
| "Wrap region in quote block"
| (interactive)
| (save-excursion
| (save-restriction
| (and
|
Hello,
I've created a mode to measure the personal effectiveness in GNU/Emacs,
it's contributed in
http://orgmode.org/worg/code/elisp/org-effectiveness.el.
In the next days, I'll write a tutorial in worg to use it. I would like
contribute it to contrib, I hope receive comments.
Thanks!
--
Dav
Hi Tristan,
don't get me wrong. Being married to a Chinese and lived in Japan for many
years I know exactly what you are talking about ;)
I just feel it needs some clean and well defined way how to implement all
those different export features without cluttering the basic exporters.
Somehow the s
Am Dienstag, 28. Mai 2013, 18:06:54 schrieb Thorsten Jolitz:
> Thorsten Jolitz writes:
>
> PS
> There was one wrong paren, better use this one instead:
>
> ,---
>
> | (defun org-wrap-region-in-quote-block ()
> |
> | "Wrap region in quot
Hello,
Listings should use the LaTeX flavor of the TeX language for `latex' code
blocks.
Here is the patch therefore.
Best regards,
Seb
>From 0be53f74dd665600229f7ac81b3e548718846658 Mon Sep 17 00:00:00 2001
From: Sebastien Vauban
Date: Tue, 28 May 2013 21:14:33 +0200
Subject: [PATCH] Add La
davi...@es.gnu.org (David Arroyo =?utf-8?Q?Men=C3=A9ndez?=) writes:
> Hello,
>
> The spanish version of orgguide is good maintained and from my point of
> view would be useful to the spanish org people add a link to
> http://orgmode.org/#docs. For instance:
>
> Read the compact guide in spanish:
This might not be reproducible as all I can do is give general information.
I am getting "Please regenerate the refile cache with `C-0 C-c C-w'"
quite a lot recently. Git master.
I use the refile cache and I also do restricted refile to :refile: and
I use a verify function.
I use magit.el.
I k
Thorsten Jolitz writes:
> Thorsten Jolitz writes:
>
>> Karl Voit writes:
>>
>>> Hi!
>>>
>>> I could not find anything yet which says that it's possible (or not)
>>> to define a file variable which enables PROPERTY drawers to be
>>> expanded (only in this current file).
>>>
>>> My use case: I us
27 matches
Mail list logo
