Hello. Thanks everyone for explaining that Bash can't have effect on
other processes stderr.
Chet, yes I certainly think it would be a good feature enabling more
colorization in Bash's own output. About the other types of information
you pointed out I think that's a good idea to consider them
2020-09-15 10:59 Budi :
> simply run a readline function among lines codes of bash script such
> a menu-complete, or previous-history repeated thrice, or etc
What is not clear is not how you call the readline function, but what
kind of ``script'' do you assume?
a. If it is the normal executable s
> On Sep 14, 2020, at 9:59 PM, Budi wrote:
>
> simply run a readline function among lines codes of bash script such a
> menu-complete, or previous-history repeated thrice, or etc
That doesn't really answer Greg's question. What larger task are
you trying to accomplish by invoking readline functi
simply run a readline function among lines codes of bash script such a
menu-complete, or previous-history repeated thrice, or etc
On 9/15/20, Budi wrote:
> simply run a readline function among lines codes of bash script such a
> menu-complete, or menu-complete repeated thrice, or etc etc
>
> On 9
simply run a readline function among lines codes of bash script such a
menu-complete, or menu-complete repeated thrice, or etc etc
On 9/14/20, Greg Wooledge wrote:
> On Mon, Sep 14, 2020 at 10:09:16PM +0700, Budi wrote:
>> How to do a readline function execution inside bash script as mimic to
>>
Date:Mon, 14 Sep 2020 12:04:02 -0400
From:Chet Ramey
Message-ID: <6377c2e5-b496-8a80-2f86-d70a6f825...@case.edu>
| "However, the double-quote character ( '"' ) [edited, since the HTML on the
| web site is malformed]
So it is, what a mess, the pdf formatted versi
On 9/13/20 4:51 PM, Robert Elz wrote:
> | The specific construct is
> |
> | P=A
> | cat < | ${P+\"$P\"}
> | EOF
>
> That should output \"A\"
OK, let's discuss it.
>
> | In this case, the usual proscription on double quotes in here-documents
> | does not apply, since the double
On 9/13/20 2:45 PM, Andreas Schwab wrote:
> You have a regression here though:
>
> cat < \"
> EOF
Thanks, you're right. I'll take a look.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...
On Mon, Sep 14, 2020 at 10:09:16PM +0700, Budi wrote:
> How to do a readline function execution inside bash script as mimic to
> actual key press ?
Please tell us what you're actually trying to do. It makes a huge
difference.
You said "script", so I guess you don't want to pre-populate the input
How to do a readline function execution inside bash script as mimic to
actual key press ?
On 9/13/20 5:59 AM, A M wrote:
> Hello, I would like to submit a feature request/suggestion on Bash. (I was
> told submitting to this mailing list was the right way to do it.)
>
> Feature request: Enable possibility of colored stderr output.
Let's separate the two cases: bash coloring its own out
>
> Yes, thanks. It's a typo, but has no effect on obtaining the right answer.
> On some weird yet-to-be-encountered system, if the exit status were not
> available at some offset in the status word, it would result in an infinite
> loop.
>
Indeed, and that's what I observed. Trying to figure out
On 9/13/20 6:17 PM, Andreas K. Hüttel wrote:
> Hi,
>
> in aclocal.m4 (and thus also configure), the test for
> BASH_STRUCT_WEXITSTATUS_OFFSET contains
>
> /* crack s */
> for (i = 0; i < (sizeof(s) - 8); i++)
>
> Shouldnt this be
>
> /* crack s */
> for (i = 0; i < (sizeof(s) * 8); i
On Sun, Sep 13, 2020 at 11:59:45AM +0200, A M wrote:
> Feature request: Enable possibility of colored stderr output.
Not possible. Output does not "pass through" bash on the way to the
terminal. Bash is like a plumber or a switchboard operator. Bash just
screws all the pipes together, or plugs
14 matches
Mail list logo
