Groups | Search | Server Info | Login | Register
Groups > comp.mail.pine > #3146
| From | D <nospam@example.net> |
|---|---|
| Newsgroups | comp.mail.pine |
| Subject | Re: 2 small annoyances, maybe possible future features? |
| Date | 2025-01-15 09:54 +0100 |
| Organization | i2pn2 (i2pn.org) |
| Message-ID | <bfdb684f-22d9-80a3-acb9-cd67123fe715@example.net> (permalink) |
| References | <b68d81f5-c9f6-17e2-a9dd-fcebd6ba992b@example.net> <64803103-e2c2-1b99-3320-a134428e1840@washington.edu> <71bd5bc8-c608-7661-db64-09ccf71d8df4@example.net> <8fff906c-1115-a933-8d3e-1b13bc9a5748@washington.edu> |
On Tue, 14 Jan 2025, Eduardo Chappa wrote: > On Tue, 14 Jan 2025, D wrote: > >> On Mon, 13 Jan 2025, Eduardo Chappa wrote: >> >>> the same happens with error messages. alpine makes sure that you see error >>> messages, and it enforces those 3 seconds by locking the program and not >>> letting you do anything else. that is what you are experiencing. >> >> Just to expand a bit on this, in case anyone else ever reads this in the >> future... >> >> After a bit of grepping around the source I found the following on line 121 >> in >> the file status.c: >> >> /* >> * By convention, we have min_time equal to zero in messages which we >> * think are not as important, so-called comfort messages. We have >> * min_time >= 3 for messages which we think the user should see for >> * sure. Some users don't like to wait so we've provided a way for them >> * to live on the edge. >> * status_msg_delay == -1 => min time == MIN(0, min_time) >> * status_msg_delay == -2 => min time == MIN(1, min_time) >> * status_msg_delay == -3 => min time == MIN(2, min_time) >> * ... >> */ >> if(ps_global->status_msg_delay < 0) >> min_time = MIN(-1 - ps_global->status_msg_delay, min_time); > > oh, this is an interesting finding. there is a variable in the .pinerc file > called status-message-delay, which when set to a negative value will reduce > the amount of time the message is displayed in the screen. > > if you set this value to -2, you will get a delay of 1 second, which will > probably do what you want, and that way you do not have to rebuild alpine to > get this behavior. > > i hope this helps. I did try the compile strategy and it worked perfectly! Thank you Eduardo, setting the value in pinerc is an even better solution, since I would not have to make the change and recompile when I upgrade alpine. =) Thank you very much!
Back to comp.mail.pine | Previous | Next — Previous in thread | Find similar
2 small annoyances, maybe possible future features? D <nospam@example.net> - 2025-01-13 16:34 +0100
Re: 2 small annoyances, maybe possible future features? Eduardo Chappa <chappa@washington.edu> - 2025-01-13 21:57 -0700
Re: 2 small annoyances, maybe possible future features? D <nospam@example.net> - 2025-01-14 19:20 +0100
Re: 2 small annoyances, maybe possible future features? D <nospam@example.net> - 2025-01-14 22:57 +0100
Re: 2 small annoyances, maybe possible future features? Eduardo Chappa <chappa@washington.edu> - 2025-01-14 20:15 -0700
Re: 2 small annoyances, maybe possible future features? D <nospam@example.net> - 2025-01-15 09:54 +0100
csiph-web