Thanks for bringing me into the conversation! :) I'm so far from that
sort of thing right now. Rough activity tracking by buttons and voice
shortcuts on my phone is all I can manage with a toddler around.
Marcin, I wonder if you might like to adapt some code from
sachachua.com/dotemacs for clo
On 2018-10-16 at 16:59, John Kitchin wrote:
> This might be going the opposite direction, but I worked on a way to make
> it easier to digest the output of Python in elisp, in these two posts:
>
> http://kitchingroup.cheme.cmu.edu/blog/2015/05/16/Python-data-structures-to-lisp/
> http://kitchingrou
On 10/14/18, Marcin Borkowski wrote:
> But I decided it's not worth it. Very complicated and unreliable (I
> might have two or more clocking tasks related to the same file, for
> example).
hm, it doesn't seem so to me. what do you mean by 2 or more related
to the same file? a file can have any
This might be going the opposite direction, but I worked on a way to make
it easier to digest the output of Python in elisp, in these two posts:
http://kitchingroup.cheme.cmu.edu/blog/2015/05/16/Python-data-structures-to-lisp/
http://kitchingroup.cheme.cmu.edu/blog/2016/05/30/Writing-lisp-code-fro
Thanks for sharing that, John. Glad to see John (the other one) getting
more recognition for his work!
Hi Marcin,
That sounds very geekily interesting. :) I imagine Sacha Chua might be
interested as well, although she already has a sophisticated system for
her Quantified Life stuff.
I'd be interested in looking at your code. For several years I've used
a "pomodoro"-like shell script to help sta
Nicolas Goaziou writes:
>> my understanding is that code that runs with lexical-binding enabled
>> is generally faster.
>
> Not really. But it's certainly easier to understand since it removes one
> class of problems.
>From what I've read, the byte-compiler can optimize better when
lexical-bindi
Would it be useful to begin integrating into babel functions so to
serialize lisp objects (just as prin1-to-string) in other languages?
I’ve read some babel files trying to do that, independently of each
others (that’s a lot of similar `typecase's (seeing it I’m regretting
each type-spec in it can
On 16/10/18 13:43, Nicolas Goaziou wrote:
Hello,
Use in the first column. It is a change introduced in Org 9.2.
Thank you, I expected this kind of change but could not find about it in
the docs.
Regards.
Hello,
Frederic Gilbert writes:
> To limit the width of the first column (which can be much longer than
> the example, and push the 2 other columns beyond the frame's width), I
> am used to use the width specification, as in:
>
>| Title |+ | - |
>
I should add I was in an emacs without
the .emacs customization to allow TAB
to cycle the headline visability which
explains why I could not do that, but
why C-x 5 0 was refused is a puzzle.
> Looking at the file in smerge-mode
> and then calling smerge-ediff
> produced my Org-Mode buffer
>
On Tuesday, 16 Oct 2018 at 11:46, Éric Würbel wrote:
> I think that this problem is very specific to the following case :
> - LaTeX SRC block
> - needed translation of this block into a png (and perhaps svg) image
> - preprocessing with pdflatex, so we end up with a pdf->png conversion.
It is spec
Hello,
I found myself in a situation to
smerge-ediff with three windows
split inside a frame.
There was another tiny frame with
a question mark which I didn’t do
anything to. Maybe I had to.
I had tried to git merge and there
were conflicts needing attention.
Looking at the file in smerg
Le 16/10/2018 à 09:18 GMT, Eric S Fraga a dit:
> On Tuesday, 16 Oct 2018 at 10:04, Éric Würbel wrote:
>> Hello list,
>>
>> I finally tracked down the problem. It is not related to my use of
>> latexmk. It is an Imagemagick problem. The version installed by xubuntu
>> 18.04 has a restrictive policy
On Tuesday, 16 Oct 2018 at 10:04, Éric Würbel wrote:
> Hello list,
>
> I finally tracked down the problem. It is not related to my use of
> latexmk. It is an Imagemagick problem. The version installed by xubuntu
> 18.04 has a restrictive policy on pdf files. I tweaked the
> '/etc/ImageMagick-6/poli
Hello list,
I finally tracked down the problem. It is not related to my use of
latexmk. It is an Imagemagick problem. The version installed by xubuntu
18.04 has a restrictive policy on pdf files. I tweaked the
'/etc/ImageMagick-6/policy.xml' file which contains the following policy
restriction :
On 15/10/18 21:20, Nicolas Goaziou wrote:
Hello,
Frederic Gilbert writes:
Following an upgrade from 8.2.10 to 9.1.14 from GIT repository,
it looks like tables column width specifications (e.g. <10> on a row)
don't work anymore.
Could you explain what doesn't work?
Regards,
Sorry for not
17 matches
Mail list logo
