Re: Read builtin -e (readline) oddities

2017-06-20 Thread Chet Ramey
On 6/19/17 3:40 PM, Chet Ramey wrote: >> #3 >> Hit `C-x C-e' thrice. Also, the mapping of `\C-m' became `self-insert' >> instead >> of `accept-line'. > > `read -e' changes it because it's no longer the line delimiter. > >> dualbus@debian:~$ PATH= EDITOR=: read -e -d '' >> >> PATH= EDITOR

Re: Read builtin -e (readline) oddities

2017-06-19 Thread Chet Ramey
On 6/18/17 9:39 PM, Eduardo A. Bustamante López wrote: > I'm trying to figure out a way to fuzz >>read -e -d ""<<, without having the > fuzzer break due to the temporary files created by fc. > > While doing this, I noticed the oddities described below. > > > #1 > Hit `C-x C-e' twice. The value

Re: Read builtin -e (readline) oddities

2017-06-19 Thread Chet Ramey
On 6/18/17 9:39 PM, Eduardo A. Bustamante López wrote: > #1 > Hit `C-x C-e' twice. The value of PATH seems to be ignored for the second > line. The shell should ensure that the temporary env is preserved across the entire execution of any builtin that can call parse_and_execute (like `fc' and `r

Re: Read builtin -e (readline) oddities

2017-06-19 Thread Eduardo Bustamante
On Mon, Jun 19, 2017 at 9:57 AM, Eduardo A. Bustamante López wrote: [...] > Hm, I can still reproduce it under Debian 9, using the `devel' branch, and I'm > sure no startup files are being sourced. > > dualbus@debian:~/src/gnu/bash-builds/devel$ ./bash --norc --noprofile > bash-4.4$ declare -p

Re: Read builtin -e (readline) oddities

2017-06-19 Thread Eduardo A . Bustamante López
On Mon, Jun 19, 2017 at 10:08:30AM -0400, Chet Ramey wrote: [...] > I can't reproduce this. I suspect one of your startup files is somehow > being read and setting PATH. It may also be an interaction with the > command-not-found hook. Hm, I can still reproduce it under Debian 9, using the `devel'

Re: Read builtin -e (readline) oddities

2017-06-19 Thread Chet Ramey
On 6/18/17 9:39 PM, Eduardo A. Bustamante López wrote: > I'm trying to figure out a way to fuzz >>read -e -d ""<<, without having the > fuzzer break due to the temporary files created by fc. > > While doing this, I noticed the oddities described below. > > > #1 > Hit `C-x C-e' twice. The value

Read builtin -e (readline) oddities

2017-06-18 Thread Eduardo A . Bustamante López
I'm trying to figure out a way to fuzz >>read -e -d ""<<, without having the fuzzer break due to the temporary files created by fc. While doing this, I noticed the oddities described below. #1 Hit `C-x C-e' twice. The value of PATH seems to be ignored for the second line. dualbus@debian:~$ P