From Newsgroup: comp.mail.pine

Hi,

another stupid question. I am used to use GNU ed as my editor of choice.
When prompted for my editor, I answered ed. Alpine threw me into it, I did
my thing but quitting ed did not put the content in my message buffer.

What should I do in my setup to use ed as usual ?

-Xavier
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On 2026-03-16, Xavier Maillard <x@maillard.im> wrote:

Hi,

another stupid question. I am used to use GNU ed as my editor of choice.
When prompted for my editor, I answered ed. Alpine threw me into it, I did my thing but quitting ed did not put the content in my message buffer.

What should I do in my setup to use ed as usual ?

When you use an alternative editor, the editor is invoked on the file containing the "message buffer".

Have you saved the edited text into a different file?

--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Tue, 17 Mar 2026, Jim Jackson wrote:

On 2026-03-16, Xavier Maillard <x@maillard.im> wrote:

Hi,

another stupid question. I am used to use GNU ed as my editor of choice.
When prompted for my editor, I answered ed. Alpine threw me into it, I did >> my thing but quitting ed did not put the content in my message buffer.

What should I do in my setup to use ed as usual ?

When you use an alternative editor, the editor is invoked on the file containing the "message buffer".

Have you saved the edited text into a different file?

As simple as this :) w + Ctrl D did the right thing for me.
I thought I had to save to a specific file...

Thank you for your help. Much better.
-Xavier
--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Jim Jackson <jj@franjam.org.uk> wrote:

On 2026-03-16, Xavier Maillard <x@maillard.im> wrote:

another stupid question. I am used to use GNU ed as my editor of choice. >>When prompted for my editor, I answered ed. Alpine threw me into it, I did >>my thing but quitting ed did not put the content in my message buffer.

What should I do in my setup to use ed as usual ?

When you use an alternative editor, the editor is invoked on the file >containing the "message buffer".

Have you saved the edited text into a different file?

That reminds me. If my terminal session times out while I'm composing, I
will likely lose the buffer. Yes, alpine attempts to write it out to "interrupted" but even if it works, it won't be the final state of the
buffer.

While composing, I'd like to be able to write out the buffer to a known
file in a known location from time to time, even if it's in /tmp or
~/tmp, and for the temporary file to persist after the alpine session
closes. It would save me from rewriting long messages.

Yes, yes, if it's a long message or reply, I should edit it outside the
alpine session, but I rarely do.
--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On 2026-03-17, Adam H. Kerman <ahk@chinet.com> wrote:

Jim Jackson <jj@franjam.org.uk> wrote:

On 2026-03-16, Xavier Maillard <x@maillard.im> wrote:

another stupid question. I am used to use GNU ed as my editor of choice. >>>When prompted for my editor, I answered ed. Alpine threw me into it, I did >>>my thing but quitting ed did not put the content in my message buffer.

What should I do in my setup to use ed as usual ?

When you use an alternative editor, the editor is invoked on the file >>containing the "message buffer".

Have you saved the edited text into a different file?

That reminds me. If my terminal session times out while I'm composing, I
will likely lose the buffer. Yes, alpine attempts to write it out to "interrupted" but even if it works, it won't be the final state of the buffer.

While composing, I'd like to be able to write out the buffer to a known
file in a known location from time to time, even if it's in /tmp or
~/tmp, and for the temporary file to persist after the alpine session
closes. It would save me from rewriting long messages.

Yes, yes, if it's a long message or reply, I should edit it outside the alpine session, but I rarely do.

If you are in danger of a remote connection timing out, then surely you
use something like "screen" to manage your sessions? Or have I misunderstood?

I do a lot of remote sessions, and manage ssh to use 'ServerAlive's
which keeps micky mouse NAT routers from dropping connections.

--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Jim Jackson <jj@franjam.org.uk> wrote:

. . .

If you are in danger of a remote connection timing out, then surely you
use something like "screen" to manage your sessions? Or have I misunderstood?

I get interrupted and walk away.

I do a lot of remote sessions, and manage ssh to use 'ServerAlive's
which keeps micky mouse NAT routers from dropping connections.

I've been sending keep alives every 150 seconds.
--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On 2026-03-18, Adam H. Kerman <ahk@chinet.com> wrote:

Jim Jackson <jj@franjam.org.uk> wrote:

. . .

If you are in danger of a remote connection timing out, then surely you >>use something like "screen" to manage your sessions? Or have I misunderstood?

I get interrupted and walk away.

Yes but why does it time out? Can't you set an infinite timeout?
If not then screen (there are alternatives) is your friend.

I do a lot of remote sessions, and manage ssh to use 'ServerAlive's
which keeps micky mouse NAT routers from dropping connections.

I've been sending keep alives every 150 seconds.

--- Synchronet 3.21e-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Jim Jackson <jj@franjam.org.uk> wrote:

On 2026-03-18, Adam H. Kerman <ahk@chinet.com> wrote:

Jim Jackson <jj@franjam.org.uk> wrote:

. . .

If you are in danger of a remote connection timing out, then surely you >>>use something like "screen" to manage your sessions? Or have I misunderstood?

I get interrupted and walk away.

Yes but why does it time out?

I tried on a different router. Still timed out. Must be the sleep
setting in the computer. I'll look there.

Can't you set an infinite timeout?
If not then screen (there are alternatives) is your friend.

I do a lot of remote sessions, and manage ssh to use 'ServerAlive's >>>which keeps micky mouse NAT routers from dropping connections.

I've been sending keep alives every 150 seconds.

--- Synchronet 3.21e-Linux NewsLink 1.2