Hi David,
yes. That works perfectly and solves both issues at the same time. Now
it is perfect!
.d.
David Edmondson writes:
> On Wed, Oct 29 2014, David Belohrad wrote:
>> - 'standard' behaviour is, that the email sent becomes read-only so with
>> 'q' keystroke I can bury the buffer with
a small correction. THIS:
(kill-new (concat "[[notmuch:id:" (replace-regexp-in-string "[<>]" ""
msg-id) "][" (replace-regexp-in-string "[\]\\[]" "_" subject) "]]"))
is the correct way how to make the link and the subject into the kill
ring. The thing is, that subject must not contain [] (as
dear all,
thanks for fruitful hints. Based on what you've done I have setup it as
follows:
1) the capture template, which uses clipboard buffer to setup the
data. So my org-capture-templates contains this entry:
("@" "Email outgoing sync. USED INTERNALLY" entry (file+datetree (concat
On Wed, Oct 29 2014, David Belohrad wrote:
> - 'standard' behaviour is, that the email sent becomes read-only so with
> 'q' keystroke I can bury the buffer with the email. However when I
> have implemented this, I have noticed that when I 'confirm' the
> template, I go back into the buffer
dear all,
thanks for fruitful hints. Based on what you've done I have setup it as
follows:
1) the capture template, which uses clipboard buffer to setup the
data. So my org-capture-templates contains this entry:
(@ Email outgoing sync. USED INTERNALLY entry (file+datetree (concat
a small correction. THIS:
(kill-new (concat [[notmuch:id: (replace-regexp-in-string []
msg-id) ][ (replace-regexp-in-string [\]\\[] _ subject) ]]))
is the correct way how to make the link and the subject into the kill
ring. The thing is, that subject must not contain [] (as e.g. [O]) so I
have
On Wed, Oct 29 2014, David Belohrad wrote:
- 'standard' behaviour is, that the email sent becomes read-only so with
'q' keystroke I can bury the buffer with the email. However when I
have implemented this, I have noticed that when I 'confirm' the
template, I go back into the buffer 'sent
Hi David,
yes. That works perfectly and solves both issues at the same time. Now
it is perfect!
.d.
David Edmondson d...@dme.org writes:
On Wed, Oct 29 2014, David Belohrad wrote:
- 'standard' behaviour is, that the email sent becomes read-only so with
'q' keystroke I can bury the
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
> David Belohrad writes:
>
>> Dear All,
>>
>> i'm using org. And I'm using notmuch (that's why I address both mailing
>> lists). Now, writing an email in everyday bussiness requires a
>> non-significant time of your workhours. So I'd like to have this
David Edmondson writes:
> On Fri, Oct 24 2014, Eric Abrahamsen wrote:
>> David Belohrad writes:
>>
>>> Dear All,
>>>
>>> i'm using org. And I'm using notmuch (that's why I address both mailing
>>> lists). Now, writing an email in everyday bussiness requires a
>>> non-significant time of your
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
David Belohrad da...@belohrad.ch writes:
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time of your workhours. So I'd like to have
David Edmondson d...@dme.org writes:
On Fri, Oct 24 2014, Eric Abrahamsen wrote:
David Belohrad da...@belohrad.ch writes:
Dear All,
i'm using org. And I'm using notmuch (that's why I address both mailing
lists). Now, writing an email in everyday bussiness requires a
non-significant time
12 matches
Mail list logo
