> In the US we call those "parentheses", and we reserve the word "brackets"
> (or "square brackets") for [ ]. I realize that the UK uses different
> terminology. Hence, the word is ambiguous and you should always type
> the actual characters you mean.
These are also "paréntesis" in Spanish, so it
On 8/7/15 3:21 PM, Nellis, Kenneth wrote:
>> Since you're adding the non-visible characters to the prompt, you can
>> try bracketing them with \001 and \002, but you have to do that yourself.
>>
> Hey, that works! Thanx! Didn't see it in the documentation. My bad?
It's in the readline documentati
On Friday, August 07, 2015 3:01 PM, Chet Ramey wrote:
> On 8/7/15 9:36 AM, Nellis, Kenneth wrote:
> > Bash Version: 4.3
> > Patch Level: 39
> > Release Status: release
> >
> > Description:
> > Pressing CTRL-U after entering data in response to a read -ep prompt
> should work as does the PS1 bash pr
On 8/7/15 9:36 AM, Nellis, Kenneth wrote:
> Bash Version: 4.3
> Patch Level: 39
> Release Status: release
>
> Description:
> Pressing CTRL-U after entering data in response to a read -ep prompt should
> work as does the PS1 bash prompt.
> Consider a custom PS1 bash prompt containing ansi escape s
On 8/4/15 8:08 AM, Christian Neukirchen wrote:
> Hi,
>
> I noticed that the following script keeps executing (and outputs
> "oops") in Bash 4.3.39(1)-release and 2.05b.13(1)-release, in
> difference to dash-0.5.8, mksh-R51, busybox sh v1.23.2, ksh-2012.08.01,
> and zsh-5.0.8:
>
> echo ${x!y}
> ec
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -D
On Thu, Aug 06, 2015 at 07:45:53PM +0200, Valentin Schmidt wrote:
> Bash displays strange characters (including command prompt) (see attached
> png file) after the execution of the base64 (GNU coreutils 8.21) command
> like described as follows:
> base64 -d base64.txt
Xterm has some escape sequenc
On Fri, Aug 07, 2015 at 10:00:53AM +0200, Juanma wrote:
> El Thu 6 of Aug, Greg Wooledge profirió estas palabras:
> > I believe you are talking about the section that discusses the [[ ... ]]
> > command.
>
> Yes, you are right. And I mean, concretely, the last part:
> | Expressions may be combined
