Stephan Fabel writes:
> I'm trying to plot a table which looks like this:
>
> | Team | Bu | R | Bk | G | T | % Bu | % R | % Bk | %G |
> |---++---++++--+--+--+--|
> | Team 1| 4 | 5 | 2 | 24 | 35 | 11.4 | 14.3 | 5.7 | 68.6 |
> | Team 2|
Nicolas Goaziou writes:
> Hello,
>
> Reading a recent message on Emacs devel list, I stumbled upon this:
>
> I needed to go and look up to figure out how to read the org file
> that came with pdf-tools. It isn't that much text, and the annoying
> folding that org does for what
tbanelwebmin writes:
> I found a way to ensure full backward compatibility. I keep the same
> signature. When a table is given as a string parameter, it is inserted
> into a temporary buffer, which is then parsed. Overall, the resulting
> speed is quite satisfactory.
A, you didn't like my
akater writes:
> Done. New patch is attached.
Thanks for the update and the expanded explanations.
The patch looks good to me. As a minor note for future patches, it's
easier on the receiver if you include the non-patch commentary in one of
the ways that git-am can automatically detect and
Vladimir Nikishkin writes:
> However, the manual node you're pointing to disagrees with the claim that
> those are equivalent:
>
>>If you need both a repeater and a special warning period in a deadline
>>entry, the repeater should come first and the warning period last
>> DEADLINE:
Better, thanks Daniele
Let's go for "handling very large tables"
Regards
Thierry
Le 30/04/2020 à 22:47, Daniele Nicolodi a écrit :
> Hello,
>
> On 30-04-2020 14:28, tbanelwebmin wrote:
>> * Version 9.4 (not yet released)
>> ** Miscellaneous
>> *** Faster org-table-to-lisp
>>
>> The new
Hello,
On 30-04-2020 14:28, tbanelwebmin wrote:
> * Version 9.4 (not yet released)
> ** Miscellaneous
> *** Faster org-table-to-lisp
>
> The new implementation can be more than 100 times faster. This enhances
> responsiveness of Babel or Gnuplot blocks handling thousands long tables.
Le 30/04/2020 à 10:09, Nicolas Goaziou a écrit :
> Hello,
>
> tbanelwebmin writes:
>
>> Here is an alternative, faster version of org-table-to-lisp. It can be
>> more than 100 times faster.
> Great! Thank you!
>
>> #+BEGIN_SRC elisp
>> (defun org-table-to-lisp-faster ( org-table-at-p-done)
>>
I'd like to write an Org file that would export to a html with fairly
significant tweaks along the way. The rough idea is, users should be
able to run reasonaly recent vanilla emacs, (require 'ox),
(org-html-export-to-html) and get a fine-tuned html.
I also would like to move relevant Elisp to
Hello,
Nicolas Goaziou writes:
[...]
>
> It would make sense to make it easier for non-Org users who have to deal
> with Org files to set this variable to `showeverything'. This would also
> be on par with Outline mode, the major mode used to handle, e.g., NEWS
> file.
>
[...]
+1 from me as
> Reading a recent message on Emacs devel list, I stumbled upon this:
>
> I needed to go and look up to figure out how to read the org file
> that came with pdf-tools. It isn't that much text, and the annoying
> folding that org does for what amounts to a simple README file is
>
On Thursday, 30 Apr 2020 at 17:11, Nicolas Goaziou wrote:
> It would make sense to make it easier for non-Org users who have to deal
> with Org files to set this variable to `showeverything'. This would also
> be on par with Outline mode, the major mode used to handle, e.g., NEWS
> file.
Yes,
Hello,
Vladimir Nikishkin writes:
> There are two almost unrelated latex-using processes in org. One is
> export, the other one is generating previews.
>
> The latter one is far less demanding than the former. Previews only care
> about certain math, whereas exports may very well be super
Hello,
Reading a recent message on Emacs devel list, I stumbled upon this:
I needed to go and look up to figure out how to read the org file
that came with pdf-tools. It isn't that much text, and the annoying
folding that org does for what amounts to a simple README file is
On 4/29/20 6:49 PM, Neil Cherry wrote:
> On 4/29/20 6:30 PM, Tim Cross wrote:
>>
>> Jude DaShiell writes:
>>
>>> Two different scripts one yproxy and the other nproxy.
>>> Put the necessary running code in each.
>>>
>>> On Wed, 29 Apr 2020, Neil Cherry wrote:
>>>
Date: Wed, 29 Apr 2020
Hello,
apologies if this is the wrong group.
I'm trying to plot a table which looks like this:
| Team | Bu | R | Bk | G | T | % Bu | % R | % Bk | %G |
|---++---++++--+--+--+--|
| Team 1| 4 | 5 | 2 | 24 | 35 | 11.4 | 14.3 | 5.7 | 68.6 |
|
Hello,
tbanelwebmin writes:
> Here is an alternative, faster version of org-table-to-lisp. It can be
> more than 100 times faster.
Great! Thank you!
> #+BEGIN_SRC elisp
> (defun org-table-to-lisp-faster ( org-table-at-p-done)
> "Convert the table at point to a Lisp structure.
> The
Kyle Meyer writes:
> Thanks for the patch. Looks like a nice improvement to me.
>
> akater writes:
>
>> * lisp/org-agenda.el (org-todo-list): Use completing-read-multiple
>> instead of completing-read when selecting todo keywords to filter by
>> in Agenda.
>
> This and the rest of the lines
Hi The List.
Here is an alternative, faster version of org-table-to-lisp. It can be
more than 100 times faster.
#+BEGIN_SRC elisp
(defun org-table-to-lisp-faster ( org-table-at-p-done)
"Convert the table at point to a Lisp structure.
The structure will be a list. Each item is either the
Ah, great, thanks!
I have been looking at the wrong node all the time.
However, the manual node you're pointing to disagrees with the claim that
those are equivalent:
>If you need both a repeater and a special warning period in a deadline
>entry, the repeater should come first and the warning
20 matches
Mail list logo
