Bug report being withdrawn. I had nullglob set so unset wasn't being
invoked properly.
On Sat, Mar 4, 2017 at 9:10 PM, Isaac Good wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On 3/4/17 12:53 AM, Misaki wrote:
> 15 Mar 2015
> bash bug
> Full-width character, followed by at least one full word with a space after
> it.
>
> Example: あa a
>
> With trailing space.
>
> Typing before the full-width character causes the 'あ' to be pushed to next
> line, with a blank space on
On 3/4/17 12:53 AM, Misaki wrote:
> 05 May 2015
> Maybe related bug. If line is offset, such as due to ctrl-C while a command
> is running that doesn't doesn't cause a newline when it exits, then pasting
> a string that contains full-width characters causes the display of the
> first line to be tr
On 3/3/17 3:30 PM, Gian Piero Carrubba wrote:
> * Please cc me as I'm not subscribed.
>
> * [Fri, Mar 03, 2017 at 09:38:04AM -0500] Chet Ramey:
>> On 3/3/17 5:47 AM, Gian Piero Carrubba wrote:
>>> Hello all,
>>>
>>> this is a copy of Debian bug 838437 [0]. I'm posting it here because I
>>> failed
On 3/4/17 12:45 AM, Misaki wrote:
> Bash Version: 4.3
> Patch Level: 46
> Release Status: release
>
> Description:
> I am sorry if there is anything wrong with this report. The 'history'
> built-in command does not correctly track history numbers when you use the
> sequence 'history -r', 'his
On 3/4/17 1:04 AM, Misaki wrote:
> Variables are not saved when using a pipe because both sides are in a
> subshell environment.
If you want this to happen, enable the `lastpipe' shell option.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevi
On 3/4/17 7:15 AM, Rob la Lau wrote:
> Hello,
>
> I'm not sure whether I found a bug in Bash or in it's documentation.
>
> The documentation suggests that the arithmetic binary operator '-eq' is
> for integers ("Arg1 and arg2 may be positive or negative integers."),
> but when using it with '[[ ]
Hello,
I'm not sure whether I found a bug in Bash or in it's documentation.
The documentation suggests that the arithmetic binary operator '-eq' is
for integers ("Arg1 and arg2 may be positive or negative integers."),
but when using it with '[[ ]]' it doesn't fail on strings.
$ [[ 1 -eq 1 ]] &&
