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='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='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='bash
Of course, it's possible to alias fc to reset the trap before calling
the editor and restore after exiting, but it's a hack.
On Tue, Sep 24, 2013 at 11:18 AM, Chet Ramey wrote:
> On 9/19/13 2:12 PM, Carlos Pita wrote:
>
>> Bash Version: 4.2
>> Patch Level: 45
>>
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='bash
> $(xxx) is a word expansion, not a command. Bash will only pay attention to
> the exit status of command substitution in one case (x=$(foo)). This
> command substitution doesn't contribute to any other command's exit status,
> especially `echo', and `set -e' doesn't cause the shell to pay attent
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='bash
When you call emacsclient like this:
emacsclient -c -F "((fullscreen . maximized))"
the maximization ignores the size hints and some residual area could
be left behind, looking like a phantom modeline below the real one.
This doesn't happen when you manually or programatically maximize
emacs
Sorry bash, it wasn't you, I hit the autocompletion entry too fast,
this was for (bug-gnu-)emacs :)
On Fri, Jul 25, 2014 at 12:38 PM, Carlos Pita wrote:
> When you call emacsclient like this:
>
>emacsclient -c -F "((fullscreen . maximized))"
>
> the maximizat
Hi Chet,
consider the following program:
yyy() {
continue
}
xxx() {
while true; do
echo x
yyy
echo y
break
done
}
xxx
In the bash devel branch it will ignore the continue and echo
x
y
In the stable branch it will echo
x
x
x
x
.
.
.
forever, because the continue works
myself?
Cheers
--
Carlos
On Sat, Oct 10, 2015 at 1:51 PM, Chet Ramey wrote:
> On 10/10/15 9:36 AM, Carlos Pita wrote:
>> Hi Chet,
>>
>> consider the following program:
>>
>> yyy() {
>> continue
>> }
>>
>> xxx() {
>> while true; do
>>
> If not, would it be too difficult to do it myself?
On a second thought, it would be easier for me to just revert the
binary incompatible changes, assuming they're not too entangled with
the rest. Could you give me some hints? Thank you very much.
12 matches
Mail list logo