Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16798
| From | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: How do we intercept file saving or output to stdout directly |
| Date | 2020-08-24 14:30 +0700 |
| Message-ID | <mailman.939.1598254240.2469.bug-bash@gnu.org> (permalink) |
| References | <1598249852364-0.post@n7.nabble.com> <12939.1598254218@jinx.noi.kre.to> |
Date: Sun, 23 Aug 2020 23:17:32 -0700 (MST)
From: almahdi <budikusasi@gmail.com>
Message-ID: <1598249852364-0.post@n7.nabble.com>
| How do we intercept and redirect file saving or output to stdout directly in
| bash, just like e.g
|
| xkbcomp $DISPLAY
I think you're just experiencing an oddity with xkbcomp and if
you want to report an issue, it is with the X11 project that you
should be talking, this one has nothing to do with bash.
The problem is that xkbcomp (for whatever reason) wants to
unlink the file it is going to write to before creating a new
one, and, kind of obviously, no matter what magic name you
give, you cannot unlink stdout.
You can however do (or at least, on my system, I can do)
xkbcomp -o - $DISPLAY
and that seems to work (it is often worth testing whether "-"
works for stdin/stdout when all else has failed - programs
sometimes special case that name).
kre
Back to gnu.bash.bug | Previous | Next | Find similar
Re: How do we intercept file saving or output to stdout directly Robert Elz <kre@munnari.OZ.AU> - 2020-08-24 14:30 +0700
csiph-web