I changed my PS1 to:
(cmd):09:37:53:sah4ez@PC001:~$ printenv PS1
\e[1;95m\t\]\e[0m:\]\e[0;92m\u@\h\]\e[0m:\]\e[0;34m\w\a\]\]\e[0m$ \]
But line break still does not work:
ff09:37:56:sah4ez@PC001:~$
f
He he, I love that on the mailing list archive it replaces my host details with
"address@hidden", kinda ruins the calculations though... and it is in my
screenshots.
:D
From 9.2 Bash History Builtin:
> If @var{last} is not specified it is set to @var{first}
Missing comma after the dependent clause. It should read:
If @var{last} is not specified, it is set to @var{first}
Grammar references:
* https://www.ego4u.com/en/cram-up/writing/comma?10
* https://
On 2/2/18 9:50 AM, Sten Westerback wrote:
> Hi
>
> After trying to figure out what causes a weird bug, which i can see with
> lots of shells and connection types (local terminal on linux, ssh +
> numerous shells on AIX and putty (linux & windows)+numerous shells on AIX)
> i though i would ask m
On 2/2/18 2:39 PM, Alexander Kozlenkov wrote:
> $ printenv PS1
> \e[1;95m\t\e[0m:\[\e]0;\u@\h:
> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
There are a bunch of invisible characters at the beginning of the prompt
that aren't enclosed in
$ printenv PS1
\e[1;95m\t\e[0m:\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
$ uname -a
Linux PC001 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ bash --version
GNU ba
On 2/2/18 7:42 AM, Alexander Kozlenkov wrote:
> Hello!
> Thanks for your project!
> On days I did building bash v4.4.18 for using vi-ins-mode-string and
> vi-cmd-mode-string variables in VI mode (insert and command modes).
> But, when I print long string, line break don't work for the first input
>
On 2/2/18 6:18 AM, Odne Hellebø wrote:
> Damn :) my email is in a changelog :D Thanks :)
Credit where credit's due.
> One thing though, is it possible to stop the cursor at the point it
> gets ambiguous? As in I have function
> foobar and fooBar if I do
> foo I will get foobar and if my intent wa
Damn :) my email is in a changelog :D Thanks :)
One thing though, is it possible to stop the cursor at the point it
gets ambiguous? As in I have function
foobar and fooBar if I do
foo I will get foobar and if my intent was to execute fooBar I
will have to go back and uppercase it. I think it would
Hello!
Thanks for your project!
On days I did building bash v4.4.18 for using vi-ins-mode-string and
vi-cmd-mode-string variables in VI mode (insert and command modes).
But, when I print long string, line break don't work for the first input
line:
> (ins):15:30:03:sah4ez@PC001:~/git/bash-4.4.18
Hi
After trying to figure out what causes a weird bug, which i can see with
lots of shells and connection types (local terminal on linux, ssh +
numerous shells on AIX and putty (linux & windows)+numerous shells on AIX)
i though i would ask makers of my favorite shell.
The problem is that when
> I'm Re-sending using bashbug (though sent through Thunderbird :/) after I've
> subscribed to mailing-list, appears my first message didn't go through
Nope, I was wrong. :/ Just was very much delayed
On 2/1/18 5:48 PM, Kieran Grant wrote:
> Hi All,
>
> Found an interesting bug today,
>
> GNU bash, version 4.4.18(4)-release (x86_64-unknown-linux-gnu)
>
> When running in a graphical terminal (xterm, mate-terminal, gnome-terminal)
> set to 80x24.
> I get a SIGSEGV in rl_redisplay doing the fol
13 matches
Mail list logo
