Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer  writes:

>> Uwe Brauer  writes:
>
>> When I do M-# # writing this mail I see:
>> ,
>> | [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit
>> | with M-#
>> | (Meta-Key and #)
>> | * --text follows this line--
>> | Uwe Brauer  writes: ...[]
>> `
>
> I almost see the same but indented since I user supercite.

Isn't that the problem already?

In an org file, this:

,
| * headline
|  * headline
| hello
`

has only one headline, indentation for the * is not allowed.

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

   > Uwe Brauer  writes:

   > When I do M-# # writing this mail I see:
   > ,
   > | [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit with M-#
   > | (Meta-Key and #)
   > | * --text follows this line--
   > | Uwe Brauer  writes: ...[]
   > `

I almost see the same but indented since I user supercite. I will
deactivate it for the moment being, but I doubt this is the problem
since your function also should work for a new mail buffer not just a
reply one, am I right? So supercite should be irrelevant there.

I tried to do what I always do in such cases (at least if memory serves
me right). I put all outorg startup code in a file
start emacs -q and then load that file.

However when I do that, emacs tells me he does not find outshine and
outorg, although they are in $HOME/.emacs.d/elpa


So does emacs -q not ready anymore those files installed via the package
system. I am confused.

My outorg_init file is

,
| 
| (defvar outline-minor-mode-prefix "\M-#")
| 
| (require 'outline)
| (require 'outshine)
| 
| (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
| (add-hook 'message-mode-hook 'outline-minor-mode)
| 
| (require 'outorg)
|  
| (when (require 'outline)
|  (add-hook 'emacs-lisp-mode-hook 'outline-minor-mode)
|  (add-hook 'message-mode-hook 'outline-minor-mode))
|  
|  ;; outorg-export
|  (require 'outorg-export)
|  (require 'navi-mode)
|  ;; outshine
| 
| 
|  
|  (setq outshine-use-speed-commands t)
|  
|  ;; navi-mode
| (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
| 
| (provide 'outorg_init)
`


   > I suggest edebug then, as written, this must run successfully:

   > ,[ C-h f outorg-prepare-message-mode-buffer-for-editing RET ]
   > | outorg-prepare-message-mode-buffer-for-editing is a Lisp function in
   > | ‘outorg.el’.
   > | 
   > | (outorg-prepare-message-mode-buffer-for-editing)
   > | 
   > | Prepare an unsent-mail in a message-mode buffer for outorg.
   > | 
   > | This function assumes that ’--text follows this line--’ (or
   > | whatever is found inside variable ‘mail-header-separator’) is the
   > | first line below the message header, is always present, and never
   > | modified by the user. It turns this line into an ‘outshine’
   > | headline and out-comments all text below this line - if any.
   > `


   > Only available via github I think 

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer  writes:

 "Thorsten" == Thorsten Jolitz  writes:
>
>> A good start would be to try outshine with emacs-lisp mode.
>> With your outshine config done, write a file like foo.el
>
>> ,
>> | ;;; 1st level header
>> |  Sum
>> | (+ 1 1)
>> |  Subtract
>> | (- 2 1)
>> `
>
>> or
>
>> ,
>> | ;; * 1st level header
>> | ;; ** Sum
>> | (+ 1 1)
>> | ;; ** Subtract
>> | (- 2 1)
>> `
>
>> and see if you got headline fontification and all the outshine
>> functionality.
>
> That seems to work, I opened your outorg buffer and there everything
> worked as expected.
>
>
>> If that works, its a message-mode problem.
>> If not, a genereal problem with your config.

When I do M-# # writing this mail I see:
,
| [ *unsent followup to Uwe Brauer on gmane.emacs.orgmode* ] Exit with M-#
| (Meta-Key and #)
| * --text follows this line--
| Uwe Brauer  writes: ...[]
`

I suggest edebug then, as written, this must run successfully:

,[ C-h f outorg-prepare-message-mode-buffer-for-editing RET ]
| outorg-prepare-message-mode-buffer-for-editing is a Lisp function in
| ‘outorg.el’.
| 
| (outorg-prepare-message-mode-buffer-for-editing)
| 
| Prepare an unsent-mail in a message-mode buffer for outorg.
| 
| This function assumes that ’--text follows this line--’ (or
| whatever is found inside variable ‘mail-header-separator’) is the
| first line below the message header, is always present, and never
| modified by the user. It turns this line into an ‘outshine’
| headline and out-comments all text below this line - if any.
`

>>> [...]
>>> BTW, you recommended
>>> (require 'outorg-export)
>>> 
>>> I installed your package via the package system, so I don't see that
>>> file. Where can I obtain it from?
>
>> It's an extension to outorg:
>
> Where can I find it, only in that site? It seems not to be in elpa/melpa
> and marmelade.

Only available via github I think 

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Tim" == Tim Cross  writes:

> Yes, you need to checkout the 26 branch to get the next version to be
> released. A git branch -a will probably list all the branches and you
> should see one labelled 26 (I'm not running emacs from git at present, so
> cannot check). I believe git 26 has been in 'feature freeze' for a while
> while they try to sort out the main bugs needing to be fixed before 26.1
> can be released.

> Note also that I believe the template changes in org are not in
> the maint branch, only master. So you could try the maint btranch
> as that would at least have known bugs fixed.

Problem with the main branch is that the nice feature for the org
tables, namely very wide columns get somehow hidden, is not included

Re: [O] how do you compose mails in Gnus with org-mode

[Tim Cross]

Yes, you need to checkout the 26 branch to get the next version to be
released. A git branch -a will probably list all the branches and you
should see one labelled 26 (I'm not running emacs from git at present, so
cannot check). I believe git 26 has been in 'feature freeze' for a while
while they try to sort out the main bugs needing to be fixed before 26.1
can be released.

Note also that I believe the template changes in org are not in the maint
branch, only master. So you could try  the maint btranch as that would at
least have known bugs fixed.

On 8 March 2018 at 19:57, Uwe Brauer  wrote:

>
>> Uwe Brauer  writes:
>
>> To avoid confusion, the official release is still 25.3. The next
>> release, which is probably still a ways off, will be 26.1
>
> Thanks for the clarification. But in order to compile 26, I would need
> to checkout the 26 from the git repo? Do I understand that correctly?
>
>
>> The 27 version is really bleeding edge, containing changes which
>> are considered too risky for the next release. I'm not sure how
>> frequently bug fixes for 26.1 are merged into the development
>> branch.
>
> Well I started to use that version at a time a specific BIDI function
> was only in master but not in the official release. Later a similar
> thing occurred with vc.el.
>
>> From a previous post, I think you mentioned you were running from
>> git master from mid/late last year. If your running from git
>> master, I think you need to pull fairly regularly as bugs are
>> frequently fixed and you could be tripping over something which has
>> already been addressed.
>
> Ah no. I am running emacs git master from end of January. I am running
> the git/master version of org mode from last june. Why? Well Nic put in
> some very useful stuff in org-table (not in the official release now),
> but then later in September/October the whole template engine was
> changed in master and I could not find out you to make it work again,
> that is why I stick to that very particular org version.
>
>> I suspect you are likely to run into a number of bugs with the
>> latest development version of emacs and you are probably one of the
>> very few who are looking at bugs in that version. Good luck.
>
>
> Yeah maybe. At least this way reporting them I could contribute a bit to
> GNU emacs. :-D
>
>
>
>


-- 
regards,

Tim

--
Tim Cross

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

   > Uwe Brauer  writes:

   > To avoid confusion, the official release is still 25.3. The next
   > release, which is probably still a ways off, will be 26.1

Thanks for the clarification. But in order to compile 26, I would need
to checkout the 26 from the git repo? Do I understand that correctly?


   > The 27 version is really bleeding edge, containing changes which
   > are considered too risky for the next release. I'm not sure how
   > frequently bug fixes for 26.1 are merged into the development
   > branch.

Well I started to use that version at a time a specific BIDI function
was only in master but not in the official release. Later a similar
thing occurred with vc.el. 

   > From a previous post, I think you mentioned you were running from
   > git master from mid/late last year. If your running from git
   > master, I think you need to pull fairly regularly as bugs are
   > frequently fixed and you could be tripping over something which has
   > already been addressed.

Ah no. I am running emacs git master from end of January. I am running
the git/master version of org mode from last june. Why? Well Nic put in
some very useful stuff in org-table (not in the official release now),
but then later in September/October the whole template engine was
changed in master and I could not find out you to make it work again,
that is why I stick to that very particular org version.

   > I suspect you are likely to run into a number of bugs with the
   > latest development version of emacs and you are probably one of the
   > very few who are looking at bugs in that version. Good luck.


Yeah maybe. At least this way reporting them I could contribute a bit to
GNU emacs. :-D

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz  writes:

   > Uwe Brauer  writes:
   >> > Uwe Brauer  writes:
   >> 
   >> > Wow, emacs 27 ... I'm on Archlinux and always thought packages a
   >> > pretty
   >> > up-to-date.
   >> 
   >> Right Ubuntu officially only ships 24, which is pretty old.
   >> 
   >> Well it is directly form git master, so it is a pre release.
   >> The official release is 26.

   > Then Archlinux is not that much out of date.

   >> > Maybe outline has changed somehow between Emacs 25 and Emacs 27?
   >> > But I don't think so, the error you send is pretty typical for
   >> > incomplete configuration.
   >> 
   >> I think at the weekend, I will debug the problem. It might be that there
   >> some parts of my init file which are in conflict with your package.

   > A good start would be to try outshine with emacs-lisp mode.
   > With your outshine config done, write a file like foo.el

   > ,
   > | ;;; 1st level header
   > |  Sum
   > | (+ 1 1)
   > |  Subtract
   > | (- 2 1)
   > `

   > or

   > ,
   > | ;; * 1st level header
   > | ;; ** Sum
   > | (+ 1 1)
   > | ;; ** Subtract
   > | (- 2 1)
   > `

   > and see if you got headline fontification and all the outshine
   > functionality.

That seems to work, I opened your outorg buffer and there everything
worked as expected.


   > If that works, its a message-mode problem.
   > If not, a genereal problem with your config.

   >> [...]
   >> BTW, you recommended
   >> (require 'outorg-export)
   >> 
   >> I installed your package via the package system, so I don't see that
   >> file. Where can I obtain it from?

   > It's an extension to outorg:

Where can I find it, only in that site? It seems not to be in elpa/melpa
and marmelade.

Thanks for the pointer

Uwe 

Re: [O] how do you compose mails in Gnus with org-mode

[Tim Cross]

Uwe Brauer  writes:

>> Uwe Brauer  writes:
>
>> Wow, emacs 27 ... I'm on Archlinux and always thought packages a pretty
>> up-to-date.
>
> Right Ubuntu officially only ships 24, which is pretty old.
>
> Well it is directly form git master, so it is a pre release.
> The official release is 26.
>
To avoid confusion, the official release is still 25.3. The next
release, which is probably still a ways off, will be 26.1 The 27 version
is really bleeding edge, containing changes which are considered too
risky for the next release. I'm not sure how frequently bug fixes for
26.1 are merged into the development branch.

>> Maybe outline has changed somehow between Emacs 25 and Emacs 27?
>> But I don't think so, the error you send is pretty typical for
>> incomplete configuration.
>

>From a previous post, I think you mentioned you were running from git
master from mid/late last year. If your running from git master, I think
you need to pull fairly regularly as bugs are frequently fixed and you
could be tripping over something which has already been addressed. 

I suspect you are likely to run into a number of bugs with the latest
development version of emacs and you are probably one of the very few
who are looking at bugs in that version. Good luck.

-- 
Tim Cross

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer  writes:

>> Uwe Brauer  writes:
>
>> Wow, emacs 27 ... I'm on Archlinux and always thought packages a
>> pretty
>> up-to-date.
>
> Right Ubuntu officially only ships 24, which is pretty old.
>
> Well it is directly form git master, so it is a pre release.
> The official release is 26.

Then Archlinux is not that much out of date.

>> Maybe outline has changed somehow between Emacs 25 and Emacs 27?
>> But I don't think so, the error you send is pretty typical for
>> incomplete configuration.
>
> I think at the weekend, I will debug the problem. It might be that there
> some parts of my init file which are in conflict with your package.

A good start would be to try outshine with emacs-lisp mode.
With your outshine config done, write a file like foo.el

,
| ;;; 1st level header
|  Sum
| (+ 1 1)
|  Subtract
| (- 2 1)
`

or

,
| ;; * 1st level header
| ;; ** Sum
| (+ 1 1)
| ;; ** Subtract
| (- 2 1)
`

and see if you got headline fontification and all the outshine
functionality.

If that works, its a message-mode problem.
If not, a genereal problem with your config.

> [...]
> BTW, you recommended
>   (require 'outorg-export)
>
> I installed your package via the package system, so I don't see that
> file. Where can I obtain it from?

It's an extension to outorg:

,
| ;;; outorg-export.el -- Automated exporting through org
| 
| ;; Author: Jonathan Leech-Pepin https://github.com/jleechpe/outorg-export
| 
|  MetaData
| ;; :PROPERTIES:
| ;; :copyright: Jonathan Leech-Pepin
| ;; :copyright-years: 2014+
| ;; :version:  0.3
| ;; :licence:  GPLv3 or later
| ;; :licence-url: http://www.gnu.org/licenses/
| ;; :part-of-emacs: no
| ;; :author:   Jonathan Leech-Pepin
| ;; :author_email: jonathan.leechpepin AT gmail DOT com
| ;; :keywords: emacs org-mode export
| ;; :END:
`

This is the README

,
| outorg-export
| =
| 
| Automated exporting of sections of source files to any format org can export 
to.
`

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

   > Uwe Brauer  writes:

   > Wow, emacs 27 ... I'm on Archlinux and always thought packages a pretty
   > up-to-date.

Right Ubuntu officially only ships 24, which is pretty old.

Well it is directly form git master, so it is a pre release.
The official release is 26.

   > Maybe outline has changed somehow between Emacs 25 and Emacs 27?
   > But I don't think so, the error you send is pretty typical for
   > incomplete configuration.

I think at the weekend, I will debug the problem. It might be that there
some parts of my init file which are in conflict with your package.

   > is typical when 

   > ,
   > | outorg-prepare-message-mode-buffer-for-editing ()
   > `

   > has not run, it turns this line into a 1st level org headline thus
   > converting any kind of message body into an org file.

   > ,
   > | * --text follows this line--
   > | Uwe Brauer  writes:
   > `

   > without this, the error is justified - an org file without a single 
   > org headline is no org file at all.

   > You could try to write an email with these lines:

   > ,
   > | * 1st level
   > | ** 2nd level
   > | some text
   > `

   > put point on some text an call outorg, to see if it works.

ok
   > Another option would be to use edebug:
   > open outorg.el, put point into 'outorg-edit-as-org', and call M-x
   > edebug-defun. Then convert an email again, and go step-by-step with
   > SPACE key, and see how far you get.

Right.

BTW, you recommended
  (require 'outorg-export)

I installed your package via the package system, so I don't see that
file. Where can I obtain it from?

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer  writes:

 "Thorsten" == Thorsten Jolitz  writes:
>
>> Uwe Brauer  writes:
>> "Thorsten" == Thorsten Jolitz  writes:
>>> 
>>> > Joseph Vidal-Rosset  writes:
>>> > Hallo
>>> 
>>> >> I know that the subject of my email exists already.
>>> >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>>> 
>>> > This works perfectly for your subject:
>>> 
>>> I just realised that you are the author of that package. Sorry.
>>> 
>>> I set
>>> 
>>> (require 'outorg)  
>>> (require 'outshine)
>>> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>>> 
>>> (add-hook 'message-mode-hook 'outline-minor-mode)
>
>> ok, maybe I answered the wrong message, does not look that incomplete
>> actually. Maybe try a copy of my config.
>
>> I used outorg-edit-as-org to insert and evaluate these source blocks
>> directly in this email, so for me it works:
> I still can't
>
>> #+BEGIN_SRC emacs-lisp  
>>  (emacs-version)
>> #+END_SRC
>
>
>> #+results:
>> : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
>> :  of 2018-02-09
>
>
> GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d
> scroll bars)
>  of 2018-01-25"

Wow, emacs 27 ... I'm on Archlinux and always thought packages a pretty
up-to-date.

Maybe outline has changed somehow between Emacs 25 and Emacs 27?
But I don't think so, the error you send is pretty typical for
incomplete configuration.

> Debugger entered--Lisp error: (error "Before first heading")
>   signal(error ("Before first heading"))
>   error("Before first heading")
>   outline-back-to-heading()

is typical when 

,
| outorg-prepare-message-mode-buffer-for-editing ()
`

has not run, it turns this line into a 1st level org headline thus
converting any kind of message body into an org file.

,
| * --text follows this line--
| Uwe Brauer  writes:
`

without this, the error is justified - an org file without a single 
org headline is no org file at all.

You could try to write an email with these lines:

,
| * 1st level
| ** 2nd level
| some text
`

put point on some text an call outorg, to see if it works.

Another option would be to use edebug:
open outorg.el, put point into 'outorg-edit-as-org', and call M-x
edebug-defun. Then convert an email again, and go step-by-step with
SPACE key, and see how far you get.

When done, call 'load-library' on outorg.el to get rid of edebug
instrumentation.

>> #+BEGIN_SRC emacs-lisp  
>>  (org-version)
>> #+END_SRC
>
> Git master from June 2017 so relatively recent
>
>> #+results:
>> : 8.2.10
>
>> #+BEGIN_SRC emacs-lisp  
>>  (gnus-version)
>> #+END_SRC
>
>> #+results:
>> : Gnus v5.13
>
> The same here.
>
>>> But when I fire up outorg-edit-as-org in a reply message I obtain the
>>> error I described in my earlier message.
>>> 
>>> Uwe Brauer 
>
>
>

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

   > Thorsten Jolitz  writes:

   > PS
   > you do have this variable defined, right?

   > ,
   > | mail-header-separator is a variable defined in ‘sendmail.el’.
   > | Its value is "--text follows this line--"
   > | 
   > | Documentation:
   > | Line used to separate headers from text in messages being composed.
   > | 
   > | You can customize this variable.
   > `

   > the value is not important, but it can't be nil.

Yes 

,
| mail-header-separator is a variable defined in ‘sendmail.el’.
| Its value is "--text follows this line--"
| 
| Documentation:
| Line used to separate headers from text in messages being composed.
| 
| You can customize this variable.
| 
| [back]
`

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz  writes:

> Uwe Brauer  writes:
> "Thorsten" == Thorsten Jolitz  writes:
>> 
>> > Joseph Vidal-Rosset  writes:
>> > Hallo
>> 
>> >> I know that the subject of my email exists already.
>> >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>> 
>> > This works perfectly for your subject:
>> 
>> I just realised that you are the author of that package. Sorry.
>> 
>> I set
>> 
>> (require 'outorg)  
>> (require 'outshine)
>> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>> 
>> (add-hook 'message-mode-hook 'outline-minor-mode)

> ok, maybe I answered the wrong message, does not look that incomplete
> actually. Maybe try a copy of my config.

> I used outorg-edit-as-org to insert and evaluate these source blocks
> directly in this email, so for me it works:
I still can't

> #+BEGIN_SRC emacs-lisp  
>  (emacs-version)
> #+END_SRC


> #+results:
> : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
> :  of 2018-02-09


GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2018-01-25"



> #+BEGIN_SRC emacs-lisp  
>  (org-version)
> #+END_SRC

Git master from June 2017 so relatively recent

> #+results:
> : 8.2.10

> #+BEGIN_SRC emacs-lisp  
>  (gnus-version)
> #+END_SRC

> #+results:
> : Gnus v5.13

The same here.

>> But when I fire up outorg-edit-as-org in a reply message I obtain the
>> error I described in my earlier message.
>> 
>> Uwe Brauer 

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Thorsten Jolitz  writes:

> Uwe Brauer  writes:
>
> "Thorsten" == Thorsten Jolitz  writes:
>>
>>> Joseph Vidal-Rosset  writes:
>>> Hallo
>>
>>>> I know that the subject of my email exists already.
>>>> 
>> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>>
>>> This works perfectly for your subject:
>>
>> I just realised that you are the author of that package. Sorry.
>>
>> I set
>>
>> (require 'outorg)  
>> (require 'outshine)
>> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>>
>> (add-hook 'message-mode-hook 'outline-minor-mode)

PS
you do have this variable defined, right?

,
| mail-header-separator is a variable defined in ‘sendmail.el’.
| Its value is "--text follows this line--"
| 
| Documentation:
| Line used to separate headers from text in messages being composed.
| 
| You can customize this variable.
`

the value is not important, but it can't be nil.

> ok, maybe I answered the wrong message, does not look that incomplete
> actually. Maybe try a copy of my config.
>
> I used outorg-edit-as-org to insert and evaluate these source blocks
> directly in this email, so for me it works:
>
> #+BEGIN_SRC emacs-lisp  
>  (emacs-version)
> #+END_SRC
>
>
> #+results:
> : GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
> :  of 2018-02-09
>
> #+BEGIN_SRC emacs-lisp  
>  (org-version)
> #+END_SRC
>
>
> #+results:
> : 8.2.10
>
> #+BEGIN_SRC emacs-lisp  
>  (gnus-version)
> #+END_SRC
>
> #+results:
> : Gnus v5.13
>
>> But when I fire up outorg-edit-as-org in a reply message I obtain the
>> error I described in my earlier message.
>>
>> Uwe Brauer 

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Uwe Brauer  writes:

 "Thorsten" == Thorsten Jolitz  writes:
>
>> Joseph Vidal-Rosset  writes:
>> Hallo
>
>>> I know that the subject of my email exists already.
>>> 
> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]
>
>> This works perfectly for your subject:
>
> I just realised that you are the author of that package. Sorry.
>
> I set
>
> (require 'outorg)  
> (require 'outshine)
> (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>
> (add-hook 'message-mode-hook 'outline-minor-mode)

ok, maybe I answered the wrong message, does not look that incomplete
actually. Maybe try a copy of my config.

I used outorg-edit-as-org to insert and evaluate these source blocks
directly in this email, so for me it works:

#+BEGIN_SRC emacs-lisp  
 (emacs-version)
#+END_SRC

#+results:
: GNU Emacs 25.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.26)
:  of 2018-02-09

#+BEGIN_SRC emacs-lisp  
 (org-version)
#+END_SRC

#+results:
: 8.2.10

#+BEGIN_SRC emacs-lisp  
 (gnus-version)
#+END_SRC

#+results:
: Gnus v5.13

> But when I fire up outorg-edit-as-org in a reply message I obtain the
> error I described in my earlier message.
>
> Uwe Brauer 


-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Uwe Brauer]

>>> "Thorsten" == Thorsten Jolitz  writes:

   > Joseph Vidal-Rosset  writes:
   > Hallo

   >> I know that the subject of my email exists already.
   >> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

   > This works perfectly for your subject:

I just realised that you are the author of that package. Sorry.

I set

(require 'outorg)  
(require 'outshine)
(add-hook 'outline-minor-mode-hook 'outshine-hook-function)

(add-hook 'message-mode-hook 'outline-minor-mode)

But when I fire up outorg-edit-as-org in a reply message I obtain the
error I described in my earlier message.

Uwe Brauer 

Re: [O] how do you compose mails in Gnus with org-mode

[Thorsten Jolitz]

Joseph Vidal-Rosset  writes:

Hallo

> I know that the subject of my email exists already.
> [[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

This works perfectly for your subject:

,[ C-h f outorg-edit-as-org RET ]
| outorg-edit-as-org is an interactive Lisp function in ‘outorg.el’.
| 
| It is bound to M-# #,   .
| 
| (outorg-edit-as-org  ARG)
| 
| Convert and copy to temporary Org buffer
| 
| With ARG, act conditional on the raw value of ARG:
| 
| | prefix | raw | action 1  | action 2   |
| |+-+---+|
| | C-u| (4) | edit-whole-buffer | ---|
| | C-1|   1 | edit-whole-buffer | insert default export-template |
| | C-2|   2 | edit-whole-buffer | prompt user for template-file  |
| | C-3|   3 | edit-whole-buffer | insert & keep default template |
| | C-4|   4 | edit-whole-buffer | insert & keep template-file|
| | C-5|   5 | propagate changes | ---|
| 
| [back]
`

It has already been described several time how to configure
outshine/outorg that it works with message-mode too.

Its actually quite easy. Configure outshine like described in the
README, and add outline-minor-mode to message-mode-hook in your .emacs.

,
| (add-hook 'emacs-lisp-mode-hook 'outline-minor-mode)
| (add-hook 'message-mode-hook 'outline-minor-mode))
`

Then with M-# # your email (open in message-mode, gnus) will be opened
in an org-mode buffer for editing in org-mode.

Looks very similar to opening a source-block in org-mode to edit the
sources in the programming language mode.

,
| [ *unsent followup to Joseph Vidal-Rosset on gmane.emacs.orgmode* ] 
| Exit with M-# (Meta-Key and #)
| * --text follows this line--
| Joseph Vidal-Rosset  writes:
| 
| Hallo
| 
| > I know that the subject of my email exists already.
| > https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html
| 
| This works perfectly for your subject:  [...]
`

and tells you how to exit again: M-#

-- 
cheers,
Thorsten

Re: [O] how do you compose mails in Gnus with org-mode

[Eric S Fraga]

On Thursday,  1 Mar 2018 at 14:37, Joseph Vidal-Rosset wrote:
> Supposing that I want to reply
> to an email, I  would be glad to write my reply in  a org file and, once
> finished this reply,  going back to gnus to be  able to org-mime-htmlize
> it and send it.
> At the moment the only solution that I  have is to quit gnus in order to
> make an org file that I copy and paste in the reply. 

You don't have to quit gnus or even switch to another
buffer/file.  Simply change the mode to org (M-x org-mode RET), compose
your email, switch back to message mode (M-x message-mode RET), htmlize
the email and send it.

-- 
Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-352-g92176c


signature.asc
Description: PGP signature

[O] how do you compose mails in Gnus with org-mode

[Joseph Vidal-Rosset]

Hello,

I know that the subject of my email exists already.
[[https://lists.gnu.org/archive/html/emacs-orgmode/2009-08/msg00855.html]]

But  I'm  loosing  to  much  time   in  searching  the  solution  of  my
"problem". I would be happy to get in Gnus the same function that exists
in mu4e that is org-mu4e-compose-org-mode.  Supposing that I want to reply
to an email, I  would be glad to write my reply in  a org file and, once
finished this reply,  going back to gnus to be  able to org-mime-htmlize
it and send it.
At the moment the only solution that I  have is to quit gnus in order to
make an org file that I copy and paste in the reply. I am convinced that
a better solution  exists, but I am  unable to find it  (ideally the org
file for such a reply would contain the bibliography link by default).

Your help will be very welcome,

Best wishes,

Jo.