Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Show key headers only | View raw
D <nospam@example.net> writes: > On Wed, 26 Mar 2025, Salvador Mirzo wrote: > >>> Alpine. Check it out here: alpineapp.email. Eduardo, the current >>> maintainer is active from time to time on the usenet group for alpine, >>> and gives great help! >>> >>> It's written in C, compiles very easily (at least for me), and is >>> quite "hackable". =) >> >> It's a TUI, right? I kinda like to compose a message, stop on it, keep >> it open, visible, get back to the the inbox, search some stuff, open >> other messages, perhaps compose new (quick) messages, send them out, >> look at my previous message being composed and continue with writing >> it... >> >> So a TUI usually means I must draft the on-going message, get it out of >> the way so I can continue the use the application. For that reason >> alone, I think I need a GUI one. > > Ahh... yes. The closest you can get in alpine is "postpone" > messages. So I write, then I postpone it, which means it gets saved in > a special folder. I can then continue to do other stuff, and once I > hit "C" for compose, alpine asks if I want to compose a new message or > finish a saved on, and I have then a list of saved messages. It is a > TUI in the terminal, so not possible to have several open messages in > parallel I'm afraid. Nevertheless, this idea of showing a menu of saved drafts to continue the composition is quite a nice workaround.
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Re: Schneier, Data and Goliath: no hope for privacy Salvador Mirzo <smirzo@example.com> - 2025-02-23 23:28 -0300
Re: Schneier, Data and Goliath: no hope for privacy D <nospam@example.net> - 2025-02-24 11:12 +0100
Re: Schneier, Data and Goliath: no hope for privacy Salvador Mirzo <smirzo@example.com> - 2025-02-24 14:08 -0300
Re: Schneier, Data and Goliath: no hope for privacy D <nospam@example.net> - 2025-02-24 23:32 +0100
Re: Schneier, Data and Goliath: no hope for privacy Salvador Mirzo <smirzo@example.com> - 2025-02-24 22:22 -0300
Re: Schneier, Data and Goliath: no hope for privacy D <nospam@example.net> - 2025-02-25 11:34 +0100
fdm, paredit and systemd (Was: Re: Schneier, Data and Goliath: no hope for privacy) Salvador Mirzo <smirzo@example.com> - 2025-02-25 13:18 -0300
Re: fdm, paredit and systemd (Was: Re: Schneier, Data and Goliath: no hope for privacy) D <nospam@example.net> - 2025-02-26 13:53 +0100
Re: fdm, paredit and systemd Salvador Mirzo <smirzo@example.com> - 2025-02-27 06:23 -0300
Re: fdm, paredit and systemd D <nospam@example.net> - 2025-02-27 15:31 +0100
Re: fdm, paredit and systemd Salvador Mirzo <smirzo@example.com> - 2025-03-07 21:10 -0300
Re: fdm, paredit and systemd D <nospam@example.net> - 2025-03-09 00:09 +0100
Re: fdm, paredit and systemd Salvador Mirzo <smirzo@example.com> - 2025-03-08 21:41 -0300
Re: fdm, paredit and systemd D <nospam@example.net> - 2025-03-09 13:32 +0100
UNIX systems (Was: Re: fdm, paredit and systemd) Salvador Mirzo <smirzo@example.com> - 2025-03-10 03:10 -0300
Re: UNIX systems (Was: Re: fdm, paredit and systemd) D <nospam@example.net> - 2025-03-10 10:54 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-10 09:08 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-11 23:09 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-13 18:17 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-16 00:03 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-16 22:41 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-18 10:50 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-21 16:26 -0300
Re: UNIX systems Matto Fransen <mattof@sdf.org> - 2025-03-21 19:53 +0000
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-24 00:11 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-21 23:37 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-24 00:34 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-25 21:49 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-26 23:24 -0300
Re: UNIX systems D <nospam@example.net> - 2025-03-29 22:31 +0100
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-29 20:40 -0300
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-22 10:11 -0300
Re: UNIX systems kludge@panix.com (Scott Dorsey) - 2025-03-25 17:40 -0400
Re: UNIX systems D <nospam@example.net> - 2025-03-25 23:04 +0100
Re: UNIX systems Charles Dagny <1800@DEV.NULL> - 2025-03-28 21:41 -0300
Re: UNIX systems onion@anon.invalid (Mr Ön!on) - 2025-03-10 15:06 +0000
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-11 11:58 -0300
Re: UNIX systems yeti <yeti@tilde.institute> - 2025-03-11 15:49 +0042
Re: UNIX systems cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 15:25 +0000
Re: UNIX systems onion@anon.invalid (Mr Ön!on) - 2025-03-11 16:24 +0000
Re: UNIX systems cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 17:30 +0000
Re: UNIX systems candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-12 22:30 +0000
Re: UNIX systems yeti <yeti@tilde.institute> - 2025-03-12 23:23 +0042
Re: UNIX systems candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-13 20:40 +0000
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-13 18:04 -0300
Re: UNIX systems cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-13 21:26 +0000
Re: UNIX systems Salvador Mirzo <smirzo@example.com> - 2025-03-14 12:23 -0300
Re: UNIX systems cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-13 01:24 +0000
Re: UNIX systems Mike Spencer <mds@bogus.nodomain.nowhere> - 2025-03-12 01:38 -0300
Re: UNIX systems snipeco.2@gmail.com (Sn!pe) - 2025-03-12 14:03 +0000
Re: UNIX systems D <nospam@example.net> - 2025-03-12 22:19 +0100
Re: UNIX systems kludge@panix.com (Scott Dorsey) - 2025-03-11 19:09 -0400
csiph-web