Date:Wed, 26 Aug 2020 08:13:52 -0400
From:Greg Wooledge
Message-ID: <20200826121352.gn...@eeg.ccf.org>
| The obvious guess is that it's to "prevent you from accidentally
| overwriting a file".
That would be what one would normally assume, but Dale didn't
show wha
On 8/25/20 8:21 PM, George R Goffe wrote:
> I could try running strace during all of this. Would it help?
It might indicate the order in which things are happening.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ram
On 8/25/20 3:47 PM, George R Goffe wrote:
> Chet,
>
> I appreciate your help with this.
>
> Do "we" know that bash IS trying to generate an alarm?
Yes, we are fairly sure that bash is trying to `ring' the bell. When I
run
bind 'set bell-style audible'
and type the common prefix of a set of fil
On Wed, Aug 26, 2020 at 12:01:26AM -0400, Dale R. Worley wrote:
> open("/dev/stdout", O_WRONLY|O_CREAT|O_EXCL, 0666) = -1 EEXIST (File exists)
> write(2, "Error:", 18Error:) = 18
> write(2, "Cannot open \"/dev/stdout\" to wri"..., 56Cannot open "/dev/stdout"
> to write
