Steffen Nurpmeso wrote:
> |$ bash ../mk/make-rules.sh su/*.c
> |(...previous lines omitted...)
> |su-018.o: $(SU_SRCDIR)su/utf.cawk: su/utf.c makes too many open files
> | input record number 18, file
> | source line number 74
>
> Ah! Of course, i had totally forgotten about this! The
Steffen Nurpmeso wrote:
> |If I make a mistake, the prompt turns into 'ERROR# ?'
>
> This is actually a configurable compile-time option. Because this
> MUA is a command line based application error messages that show
> up on standard error fly by unseen fast, and pretty often.
I never
> "set sendwait"?
Just a small addition: the s-nail option "-#" implies sendwait, too,
and may be helpful here.
Martin
--
Check out the vibrant tech
hose coloured or not, I would call
that "degeneration" :-)
Martin Neitzel
--
__
S-nail-users@lists.sourceforge.net
Hi Steffen,
> Instead you now should (with *debug* a.k.a. -d) see something like
>
> Creating dot lock for "/var/mail/steffen"
> Can't manage lock files in "/var/mail/steffen", please check permissions
> Saved 1 message in mbox
> Held 8 messages in /var/mail/steffen
>
> Would you be so
Since I updated s-nail's master branch 10 days ago (after the
"Albatross" announcment), s-nail felt unable to lock (and hence update)
my /var/mail/$USER spool file. (A classic, local, single mbox-style
nail spool.)
Upon "q"uitting, there is actually an error msg stating "could not lock
Bob Tennent wrote:
> I used to use ~b pathname to save an outgoing message to a
> specific file. This no longer works. I know I can set record
> for *all* outgoing messages but it's often convenient to
> "record" a particular message to a particular file. Can this
> be fixed
81
? f :n
A680 Steffen Nurpmeso Wed Aug 20 22:02 89/4454 Re: [S-nail] [nail-devel] F
N684 Martin Neitzel Thu Aug 21 12:01 119/5639 ┣>
N685 Steffen Nurpmeso Thu Aug 21 12:23 111/5496 ┃┗>
N686 Martin Neitzel