Re: Feature: Easily remove current command from history

On 1/4/16 1:30 PM, por...@narod.ru wrote: > Bash Version: 4.3 > Patch Level: 42 > Release Status: release > > Description: > > There should be an easy way to remove the currently selected command > from the history. Easier than `history -d'? -- ``The lyf so short, the craft so long to

Re: Feature: Easily remove current command from history

Victor Porton writes: > It should be easy to remove lines with passwords and potentially > harmful commands (like sudo with rm). C-a C-k Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for

Re: Feature: Easily remove current command from history

Take into account that many options have been provided (history -d, the space prefix, even editing .bash_history yourself). But you request a single key stroke to do this... why? If you enter a password by mistake in your shell, and it gets recorded, then you go and clean up. It's not hard to

Re: Running bash using su -c causes 100% cpu usage on one core

On 1/4/16 1:03 PM, Marcus Wichelmannn wrote: > Afaik it's a symlink to /usr/bin/mono. > > I solved my issue by replacing the line in /etc/rc.local by: > > su cubie -c "screen -S Haussteuerung -d -m > /home/cubie/Haussteuerung/Haussteuerung/run.sh" > > But this is no fix of this bug for sure.

Re: Feature: Easily remove current command from history

On Mon, Jan 04, 2016 at 09:30:37PM +0100, Piotr Grzybowski wrote: > On Mon, Jan 4, 2016 at 9:19 PM, Victor Porton wrote: > > It is important for security: > > > > It should be easy to remove lines with passwords and potentially harmful > > commands (like sudo with rm). > > never

Re: Feature: Easily remove current command from history

On 1/4/16 3:09 PM, Victor Porton wrote: > On Mon, 2016-01-04 at 14:59 -0500, Chet Ramey wrote: >> On 1/4/16 1:30 PM, por...@narod.ru wrote: >> >>> Bash Version: 4.3 Patch Level: 42 Release Status: release Description: >>> There should be an easy way to remove the currently

Re: Feature: Easily remove current command from history

On Mon, 2016-01-04 at 15:14 -0500, Chet Ramey wrote: > On 1/4/16 3:09 PM, Victor Porton wrote: > > On Mon, 2016-01-04 at 14:59 -0500, Chet Ramey wrote: > > > On 1/4/16 1:30 PM, por...@narod.ru por...@narod.ru> > > > wrote: > > > > > > > Bash Version: 4.3 Patch Level: 42 Release Status: release >

Re: Feature: Easily remove current command from history

On Mon, 2016-01-04 at 15:37 -0500, Greg Wooledge wrote: > On Mon, Jan 04, 2016 at 09:30:37PM +0100, Piotr Grzybowski wrote: > > On Mon, Jan 4, 2016 at 9:19 PM, Victor Porton > > wrote: > > > It is important for security: > > > > > > It should be easy to remove lines with

Re: Feature: Easily remove current command from history

On Mon, Jan 4, 2016 at 9:19 PM, Victor Porton wrote: > It is important for security: > > It should be easy to remove lines with passwords and potentially harmful > commands (like sudo with rm). never put your passwords in plain text in commands, thats important for security. If,

Re: Feature: Easily remove current command from history

On Mon, 2016-01-04 at 14:59 -0500, Chet Ramey wrote: > On 1/4/16 1:30 PM, por...@narod.ru wrote: > > > Bash Version: 4.3 > > Patch Level: 42 > > Release Status: release > > > > Description: > > > > There should be an easy way to remove the currently selected > > command > > from the history. >

Feature: Easily remove current command from history

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'

Re: Feature: Easily remove current command from history

On Mon, Jan 4, 2016 at 3:07 PM, Eduardo A. Bustamante López < dual...@gmail.com> wrote: > Take into account that many options have been provided (history -d, the > space > prefix, even editing .bash_history yourself). > > But you request a single key stroke to do this... why? > > If you enter a

Re: Feature: Easily remove current command from history

On Mon, Jan 4, 2016 at 4:05 PM, Dennis Williamson < dennistwilliam...@gmail.com> wrote: > > > On Mon, Jan 4, 2016 at 3:07 PM, Eduardo A. Bustamante López < > dual...@gmail.com> wrote: > >> Take into account that many options have been provided (history -d, the >> space >> prefix, even editing

Re: Running bash using su -c causes 100% cpu usage on one core

On 1/3/16 6:27 PM, Marcus Wichelmann wrote: > Hi, > > Im not sure if this is a regression because I already found another bug > report with the same symptoms from 2007, but when adding this line to the > /etc/rc.local the cpu usage of one of the two cores raises to 100%: > > su cubie -c "(cd

Re: autocd doesn't invoke customized `cd` wrapper

On 1/1/16 4:41 PM, transl8cz...@gmail.com wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > If `cd` is a function or an alias in my environment, I think autocd ought > to invoke > that instead of the raw `command cd` (like it does now). Invoking a

Re: Running bash using su -c causes 100% cpu usage on one core

Am Mo, 4. Jan, 2016 um 2:51 schrieb Eduardo A. Bustamante López : It's impossible to tell with the amount of info you provided. That's why there's a 'bashbug' script alongside bash to generate a useful bug report template. Provide: - bash version: bash --version - OS name

Re: Uniq pattern

On Thu, Dec 31, 2015 at 06:44:07PM -0600, John McKown wrote: > On Thu, Dec 31, 2015 at 6:15 PM, Val Krem wrote: > > I wanted to search a line that contains "1235" using > > grep -R "1235". > > I am getting unwanted results such as > > 01235 or 12356 and so on. > > > >

Re: Running bash using su -c causes 100% cpu usage on one core

On 1/4/16 9:01 AM, Marcus Wichelmannn wrote: utput from htop (the first process has a cpu usage of 100%): > >> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command >> 2199 cubie 20 0 44168 15484 7552 R 101. 1.7 11:45.44 /usr/bin/cli >> ./Haussteuerung What is /usr/bin/cli? It's the program

Re: Running bash using su -c causes 100% cpu usage on one core

Am Mo, 4. Jan, 2016 um 3:32 schrieb Chet Ramey : On 1/4/16 9:01 AM, Marcus Wichelmannn wrote: utput from htop (the first process has a cpu usage of 100%): PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 2199 cubie 20 0 44168 15484 7552 R 101. 1.7 11:45.44

Re: Running bash using su -c causes 100% cpu usage on one core

On Mon, Jan 04, 2016 at 07:03:39PM +0100, Marcus Wichelmannn wrote: > Am Mo, 4. Jan, 2016 um 3:32 schrieb Chet Ramey : > >What is /usr/bin/cli? It's the program that is using the CPU. > > Afaik it's a symlink to /usr/bin/mono. > > I solved my issue by replacing the line in