On 2/14/25 5:31 AM, MacBeth wrote:
Ummm, isn't this supposed to work? I'm guessing there's a technical
reason why it doesn't...?
# fails:
$ history -r <(echo 'echo bad')
It fails because the history library requires the file to be a regular
file. It tries to read and write atomically, so the r
On 2/14/25 9:48 AM, Chet Ramey wrote:
I think it's reasonable for the history builtin to report read errors here,
something like this:
bash: history: /dev/fd/63: read error: Inappropriate file type or format
The problem with this is that it errors on /dev/null, which has always
worked and is
Ummm, isn't this supposed to work? I'm guessing there's a technical
reason why it doesn't...?
# fails:
$ history -r <(echo 'echo bad')
# succeeds:
$ history -w >(cat -n)
-
$ help | head -n 1
GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin23.4.0)
$ echo 'echo good' > hist.txt
$ cat
On Fri, Feb 14, 2025 at 4:31 AM MacBeth wrote:
>
> Ummm, isn't this supposed to work? I'm guessing there's a technical
> reason why it doesn't...?
>
> # fails:
> $ history -r <(echo 'echo bad')
>
Unless the reason is due to the file seek issue as described here...?
https://unix.stackexchange.com/
is that if fifo or if nonormal file ..
.. is that another story from history .. ?
that it doesnt accept them ..
On Fri, Feb 14, 2025, 1:36 PM Greg Wooledge wrote:
> On Fri, Feb 14, 2025 at 05:19:48 -0600, MacBeth wrote:
> > On Fri, Feb 14, 2025 at 4:31 AM MacBeth
> wrote:
> > > # fails:
> > > $
On Fri, Feb 14, 2025 at 05:19:48 -0600, MacBeth wrote:
> On Fri, Feb 14, 2025 at 4:31 AM MacBeth wrote:
> > # fails:
> > $ history -r <(echo 'echo bad')
>
> Unless the reason is due to the file seek issue as described here...?
> https://unix.stackexchange.com/a/164109
hobbit:~$ echo ': testing f
it looks me cause such as it isnt a file , yes ..
On Fri, Feb 14, 2025, 12:20 PM MacBeth wrote:
> On Fri, Feb 14, 2025 at 4:31 AM MacBeth wrote:
> >
> > Ummm, isn't this supposed to work? I'm guessing there's a technical
> > reason why it doesn't...?
> >
> > # fails:
> > $ history -r <(echo 'ec
On Feb 14 2025, Dale R. Worley wrote:
> And really, that means that the effect of -r is kind of complicated and
> unintuitive.
Not really. The command uses either the supplied filename or $HISTFILE
to name the file to operate on. Other than that, the filename argument
has no effect.
--
Andrea
The function serialisation code thinks that 1 is the default file
descriptor for <> redirections, when it is actually 0.
BEFORE
$ a () { <> f ;}; declare -f a
a ()
{
0<> f
}
$ a () { 1<> f ;}; declare -f a
a ()
{
<> f
}
AFTER
$ a () { <> f ;}; d
On 2/14/25 1:28 PM, Emanuele Torre wrote:
The function serialisation code thinks that 1 is the default file
descriptor for <> redirections, when it is actually 0.
Thanks for the report and fix.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita br
Chet Ramey writes:
> It fails because the history library requires the file to be a regular
> file. It tries to read and write atomically, so the read history function
> gets the size of the history file, allocates one big buffer to hold it,
> and reads it in one go.
Though in regard to the comma
11 matches
Mail list logo
