I've just discovered that when Org results are returned in a table, they are
modified in that leading 0s are removed. Is this a feature? A bug? Is there a
workaround for this? Leading 0s are not removed if the result is a string, but
in many cases a string of numbers is still a string and shoul
Ken Mankoff writes:
> I've just discovered that when Org results are returned in a table,
> they are modified in that leading 0s are removed. Is this a feature? A
> bug? Is there a workaround for this? Leading 0s are not removed if the
> result is a string, but in many cases a string of numbers i
On 2016-07-10 at 13:18, Eric Abrahamsen wrote:
> Ken Mankoff writes:
>
>> I've just discovered that when Org results are returned in a table,
>> they are modified in that leading 0s are removed. Is this a feature? A
>> bug? Is there a workaround for this? Leading 0s are not removed if the
>> res
I'm working on an org-mode file about cancer which is 945.1kb, is
converted to a tex file of 1.0mb and a pdf of 2.0mb with 505 pages. The
conversion is done through this code snippet '(global-set-key (kbd
"s-#") 'org-latex-export-to-latex)'. There is no problem with the
conversion to tex or conver
Hi Rares
On Fri, Jul 8, 2016 at 6:06 AM, Rares Vernica wrote:
> Just to clarify, how would you fix this:
>
> | [2016-07-05 Tue]--[2016-07-06 Wed] | 1d | vsum(d) |
> | [2016-07-06 Wed]--[2016-07-07 Thu] | 1d | 2 d |
> #+TBLFM: $3=vsum(@1$-1..@0$-1)
>
> Notice the "vsum(d)" instead of the expe
On Sun, 10 Jul 2016, Ken Mankoff wrote:
I've just discovered that when Org results are returned in a table, they
are modified in that leading 0s are removed. Is this a feature? A bug?
Take your choice. The feature/bug happens deep down:
- org-babel-execute-src-block
- org-babel-execute:sh
On 2016-07-10 at 16:50, Charles C. Berry wrote:
> For the latter, send the output to a file. Maybe use :file or pipe it
> from your script.
I'm now capturing results to :file. This also make the code less dependent on
Org. I still manage all the code in Org Babel blocks, but for the following
Maybe an (too ?) obvious suggestion: Get more memory ?
On Sun, 10 Jul 2016 at 16:37 Sharon Kimble
wrote:
>
> I'm working on an org-mode file about cancer which is 945.1kb, is
> converted to a tex file of 1.0mb and a pdf of 2.0mb with 505 pages. The
> conversion is done through this code snippet
Leo Noordhuizen writes:
> Maybe an (too ?) obvious suggestion: Get more memory ?
I'm working on a computer with 16g of ram and 31g of swap, which would
be adequate for almost anything I think. At the moment getting more ram
isn't a viable option, I have to stick with what I've already got.
Than
Yes. You obviously have ample resources in that area!
Op zo 10 jul. 2016 21:05 schreef Sharon Kimble :
> Leo Noordhuizen writes:
>
> > Maybe an (too ?) obvious suggestion: Get more memory ?
>
> I'm working on a computer with 16g of ram and 31g of swap, which would
> be adequate for almost anythi
It kind of sounds like you want the button-lock package. See
http://kitchingroup.cheme.cmu.edu/blog/2015/03/18/Clickable-links-for-Twitter-handles-in-Emacs/
for example (and search "clickable text" on my blog for other examples).
Maybe something like:
#+BEGIN_SRC emacs-lisp
(require 'button-lock)
I find it sometimes helpful to narrow to a section in large documents.
On July 10, 2016, at 3:37 PM, Leo Noordhuizen wrote:
Yes. You obviously have ample resources in that area!
Op zo 10 jul. 2016 21:05 schreef Sharon Kimble :
Leo Noordhuizen writes:
> Maybe an (too ?) obvious suggestion: G
There must be something more than this. I sometimes work on a similar size
file on an HP Chromebook using emacs in a Crouton installation and have no
problems at all with speed. It is a nox emacs installation, if that matters.
Alan
On 11 July 2016 at 08:34, John Kitchin wrote:
> I find it somet
13 matches
Mail list logo