Hello folks,
browsing bash code, I found something that looks like a copy-paste typo:
#ifndef USHRT_MAX
# define UCHAR_MAX 65535
#endif
So, I thought It would be useful to drop you a note about that.
--
erra
On Mon, Sep 12, 2011 at 14:19, Roger wrote:
>> On Mon, Sep 12, 2011 at 08:36:07AM -0400, Greg Wooledge wrote:
>>On Sun, Sep 11, 2011 at 11:23:48PM -0800, Roger wrote:
>>> When using GNU Screen (or other terminal multiplexer), I noticed the
>>> terminal
>>> multiplexer never gives each bash shell
I ran into a few previous grammar errors earlier within the Bash Manual Page,
but the manual became error free at a point so I didn't bother noting them
until I got to about this point.
One thing I have noticed, most lists with embedded commas, "and's" and "or's"
are already well written! Most p
> On Mon, Sep 12, 2011 at 08:36:07AM -0400, Greg Wooledge wrote:
>On Sun, Sep 11, 2011 at 11:23:48PM -0800, Roger wrote:
>> When using GNU Screen (or other terminal multiplexer), I noticed the terminal
>> multiplexer never gives each bash shell opened, a chance to write the history
>> file on exit.
On 9/11/11 4:54 PM, Roger wrote:
> Can see POSIX compatibility is likely an issue here.
How so?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
On 9/11/11 6:37 PM, rogerx@gmail.com wrote:
>
> SHELL BUILTIN COMMANDS : compgen
>
> First paragraph
>
> Run-on sentence/Repetitive statement (aka Too wordy)
>
> Original Text: When using the -F or -C options, the various shell variables
> set by the
> programmable completion facilities,
On 9/12/11 9:22 AM, Thomas De Contes wrote:
> on the other hand, if there is a way for bash to not display special
> characters on the interactive line,
> i suppose it can be useful to know how to do that in many cases, for example
> if i switch on a new platform, waiting for making special char
Le 25 août 2011 à 15:35, Chet Ramey a écrit :
>>
>> Le 25 août 2011 à 14:17, Chet Ramey a écrit :
>>
so, wcwidth is apple's responsibility, then no libre-software developer
can do anything,
Am I right ?
>>>
>>> To a certain extent, yes. wcwidth is a libc function, and it has a
On 9/12/11 1:58 AM, Roger wrote:
> Question: Should I post this man file corrects here to the mailing list like
> this? As I read through the bash manpage, some sections are just horrible
> reading, but other sections seem really well structured.
>
> I've only fiddled with groff & much less .tex.
On Sun, Sep 11, 2011 at 11:23:48PM -0800, Roger wrote:
> When using GNU Screen (or other terminal multiplexer), I noticed the terminal
> multiplexer never gives each bash shell opened, a chance to write the history
> file on exit.
>
> The usual result after an initial install for several months, t
On 9/10/11 11:13 AM, Antoine Balestrat wrote:
> Hello !
> I've just run cppcheck (a static C/C++ code analyzer) against the latest
> bash code (freshly cloned from the git repo), and it points out some
> interesting issues.
> You can see the log here : http://pastebin.com/pZHQShJp
Thanks for the r
When using GNU Screen (or other terminal multiplexer), I noticed the terminal
multiplexer never gives each bash shell opened, a chance to write the history
file on exit.
The usual result after an initial install for several months, the history file
will
remain practically empty.
(As a temporary
12 matches
Mail list logo
