From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <zefram@fysh.org>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: About to release 3.0.7 ...
Date: Mon, 18 Oct 1999 15:48:27 +0000 [thread overview]
Message-ID: <991018154827.ZM31763@candle.brasslantern.com> (raw)
In-Reply-To: <E11d9qO-0001Vb-00@crucigera.fysh.org>
On Oct 18, 11:16am, Zefram wrote:
} Subject: Re: About to release 3.0.7 ...
}
} Jos Backus wrote:
} >+ if (limnam == "SBSIZE") { msg[limnum] = "sbsize" }
}
} This is not a good name. zsh's resource limit names tend to be more
} verbose, so you don't need to know the system to see what is being
} limited. I suggest the name "sktbuffersize".
It'd be more unixy to use "sockbufsize"; the common abbreviations are
"sock" and "buf" as in setbuf() and setsockopt(). I don't think I've
ever seen the abbreviation "skt" before. Objections?
Index: Doc/Zsh/builtins.yo
===================================================================
@@ -524,7 +524,7 @@
sitem(tt(memorylocked))(Maximum amount of memory locked in RAM.)
sitem(tt(memoryuse))(Maximum resident set size.)
sitem(tt(resident))(Maximum resident set size.)
-sitem(tt(sktbuffersize))(Maximum size of all socket buffers.)
+sitem(tt(sockbufsize))(Maximum size of all socket buffers.)
sitem(tt(stacksize))(Maximum stack size for each process.)
sitem(tt(vmemorysize))(Maximum amount of virtual memory.)
endsitem()
Index: Src/Builtins/rlimits.awk
===================================================================
@@ -34,7 +34,7 @@
if (limnam == "NPROC") { msg[limnum] = "Nmaxproc" }
if (limnam == "OFILE") { msg[limnum] = "Ndescriptors" }
if (limnam == "RSS") { msg[limnum] = "Mresident" }
- if (limnam == "SBSIZE") { msg[limnum] = "Msktbuffersize" }
+ if (limnam == "SBSIZE") { msg[limnum] = "Msockbufsize" }
if (limnam == "STACK") { msg[limnum] = "Mstacksize" }
if (limnam == "TCACHE") { msg[limnum] = "Ncachedthreads" }
if (limnam == "VMEM") { msg[limnum] = "Mvmemorysize" }
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-10-18 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-17 21:26 Bart Schaefer
1999-10-17 23:46 ` Jos Backus
1999-10-18 4:30 ` "limit sbsize" Bart Schaefer
1999-10-18 10:16 ` About to release 3.0.7 Zefram
1999-10-18 15:48 ` Bart Schaefer [this message]
1999-10-18 19:52 ` Jos Backus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=991018154827.ZM31763@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zefram@fysh.org \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).