Marcin Borkowski writes:
>> I would also suggest removing inputenc. At the moment, it is loaded
>> with the AUTO option. AFAIK, this is redundant since most recent
>> (meaning for quite a few years) TeX engines already use the encoding of
>> the file if nothing is specified.
>
> Can you elabora
Eric Abrahamsen writes:
> But how does this handle composing new blank messages?
When composing a new message it checks conditions (the first entry in a
list). So in your gnus buffer you can put your cursor on the mail group
you want to send from and it'll pick up the appropriate profile.
Thou
Rasmus writes:
> Eric Abrahamsen writes:
>
>> But how does this handle composing new blank messages?
>
> When composing a new message it checks conditions (the first entry in a
> list). So in your gnus buffer you can put your cursor on the mail group
> you want to send from and it'll pick up th
Eric Abrahamsen writes:
> Rasmus writes:
>
>> Eric Abrahamsen writes:
>>
>>> But how does this handle composing new blank messages?
>>
>> When composing a new message it checks conditions (the first entry in a
>> list). So in your gnus buffer you can put your cursor on the mail group
>> you wa
Hi,
I'm using subtree export to write letters using ox-koma. Everything
works except, all the closing statements from different subtrees get
accumulated when I export one of the subtrees.
So with the attached Org file, when I export either of the subtrees, I
get a closing line like this: \closin
On Wed, Jul 15, 2015 at 01:20:57PM +0200, Suvayu Ali wrote:
>
> I'm using subtree export to write letters using ox-koma. Everything
> works except, all the closing statements from different subtrees get
> accumulated when I export one of the subtrees.
>
> So with the attached Org file, when I ex
Hi,
Suvayu Ali writes:
> I'm using subtree export to write letters using ox-koma. Everything
> works except, all the closing statements from different subtrees get
> accumulated when I export one of the subtrees.
>
> So with the attached Org file, when I export either of the subtrees, I
> get a
I've just discovered that the slow-response is definitely related to font
locking. If I type M-x font-lock-mode to toggle it off then the typing lag
problem is solved.
According to the Emacs documentation:
'In Emacs 21 and later, turning on font-lock-mode automatically activates
the new Just-In-T
Thanks Matt! I am giving two talks in September and I was already
thinking about trying some of the html exporters instead of using beamer
as always. I will read your notes in detail.
All the best,
Julian
--
Julian Mariano Burgos, PhD
Hafrannsóknastofnun/Marine Research Institute
Skúlagata 4,
I just updated to release_8.3beta-1286-g20795fd.
``make test'' shows a failure on test 226:
--8<---cut here---start->8---
passed 225/592 test-org-babel/src-block-regexp
Updating dynamic block `clocktable' at line 2...
Updating dynamic block `clocktable' a
Nick Dokos writes:
> I just updated to release_8.3beta-1286-g20795fd.
>
> ``make test'' shows a failure on test 226:
>FAILED 226/592 test-org-clock/clocktable-until-now
>
>
> The backtrace was edited to get rid of a NUL that gnus complained
I know. I don't really understand what untilnow
Hi,
Thanks for the example.
Kyle Meyer writes:
> Sorry, I should have included an example.
>
> If I have a heading that looks like
>
> ** TODO h
> DEADLINE: <2015-07-13 Mon +3w>
>
> and I run org-todo with a numeric prefix of -1, the repeater is canceled
> by changing it to +0w:
I see.
I have a date/timestamp range:
<2015-07-13 Mon 09:00-12:00>--<2015-07-17 Fri 09:00-12:00> and
<2015-07-20 Mon 09:00-12:00>--<2015-07-24 Fri 09:00-12:00>
When I view it in the agenda:
Monday, 13 July 2015
09:00-12:00 (1/5): Some appt
...
Friday, 17 July 2015
09:00-12:00 (5/5): Some appt
But al
Manuel Koell writes:
> I have a date/timestamp range:
>
> <2015-07-13 Mon 09:00-12:00>--<2015-07-17 Fri 09:00-12:00> and
> <2015-07-20 Mon 09:00-12:00>--<2015-07-24 Fri 09:00-12:00>
>
> When I view it in the agenda:
>
> Monday, 13 July 2015
> 09:00-12:00 (1/5): Some appt
>
> ...
>
> Friday, 17 Ju
On Wed, Jul 15, 2015 at 10:36 AM, Julian Burgos wrote:
> Thanks Matt! I am giving two talks in September and I was already
> thinking about trying some of the html exporters instead of using beamer
> as always. I will read your notes in detail.
>
I really hope they're helpful! Let me know nay
I just posted another section of my emacs-init.org, here:
http://matt.hackinghistory.ca/2015/07/15/mailing-subtrees-with-attachments/
It's mostly a summary of all the help I've gotten from the list this week,
though it's just a draft really and I don't acknowledge most of your
assistance! I hope
Rasmus writes:
> Nick Dokos writes:
>
>> I just updated to release_8.3beta-1286-g20795fd.
>>
>> ``make test'' shows a failure on test 226:
>>FAILED 226/592 test-org-clock/clocktable-until-now
>>
>>
>> The backtrace was edited to get rid of a NUL that gnus complained
>
> I know. I don't re
How can I schedule my todo's more roughly? Say, I know I want to do it next
week or in a few months but I don't know the exact date nor time to do it.
I just want a way to plan more foresighted. If the week starts or the month
I could always set a more accurate timestamp then. Any idea? I tried to
Nick Dokos writes:
> Rasmus writes:
>
>> Nick Dokos writes:
>>
>>> I just updated to release_8.3beta-1286-g20795fd.
>>>
>>> ``make test'' shows a failure on test 226:
>>>FAILED 226/592 test-org-clock/clocktable-until-now
>>>
>>>
>>> The backtrace was edited to get rid of a NUL that gnus com
Nick Dokos writes:
> Rasmus writes:
>
>> Nick Dokos writes:
>>
>>> I just updated to release_8.3beta-1286-g20795fd.
>>>
>>> ``make test'' shows a failure on test 226:
>>>FAILED 226/592 test-org-clock/clocktable-until-now
>>>
>>>
>>> The backtrace was edited to get rid of a NUL that gnus c
David Engster writes:
> Nick Dokos writes:
>> Rasmus writes:
>>
>
>>> Nick Dokos writes:
>>>
I just updated to release_8.3beta-1286-g20795fd.
``make test'' shows a failure on test 226:
FAILED 226/592 test-org-clock/clocktable-until-now
The backtrace was e
On Wed, Jul 15, 2015 at 01:46:59PM +0200, Rasmus wrote:
> Suvayu Ali writes:
>
> > I'm using subtree export to write letters using ox-koma. Everything
> > works except, all the closing statements from different subtrees get
> > accumulated when I export one of the subtrees.
> >
> > So with the a
Suvayu Ali writes:
> Something like that would be a lot more logical indeed.
The attached patch allows the Romeo letter to have a heading like this:
* Yours truly,:closing:
Romeo of House Capulet
Outputting:
\setkomavar{signature}{Romeo of house Capulet}
...
\closing{You
Rasmus wrote:
> Kyle Meyer writes:
>> ** TODO h
>> DEADLINE: <2015-07-13 Mon +3w>
>>
>> and I run org-todo with a numeric prefix of -1, the repeater is canceled
>> by changing it to +0w:
>
> I see. Shouldn't org-todo rather remove the repeater?
That seems fine to me. I wonder if there
Rasmus writes:
> Eric Abrahamsen writes:
>
>> Rasmus writes:
>>
>>> Eric Abrahamsen writes:
>>>
But how does this handle composing new blank messages?
>>>
>>> When composing a new message it checks conditions (the first entry in a
>>> list). So in your gnus buffer you can put your cursor
Manuel Koell writes:
> How can I schedule my todo's more roughly? Say, I know I want to do it next
> week or in a few months but I don't know the exact date nor time to do it. I
> just want a way to plan more
> foresighted. If the week starts or the month I could always set a more
> accurate t
Rasmus writes:
> Nick Dokos writes:
>
>> Rasmus writes:
>>
>>> Nick Dokos writes:
>>>
I just updated to release_8.3beta-1286-g20795fd.
``make test'' shows a failure on test 226:
FAILED 226/592 test-org-clock/clocktable-until-now
The backtrace was edited
27 matches
Mail list logo
