Are you trying to run autocompletion on an nfs mount? Are you using ''ls''
to autocomplete and if so did you run \ls /path/to/dir .. ?
Maybe worth to mention the bash version you are using.
Op do 6 aug. 2020 19:53 schreef George R Goffe :
> Hi,
>
> I apologize for bothering you with this questi
Alright, so it seems PS1 is causing the problem. I removed the line from
~/.bashrc file and the shell is behaving normal again. Thanks for pointing
that out and apologies for the noise.
Kind regards,
Valentin
On Wed, Dec 12, 2018 at 8:56 PM Valentin Bajrami
wrote:
> Hi guys and thanks for
ORMAT\]\h:\w \[$RESET_FORMAT\]$ " " || printf %s
\[$BOLD_FORMAT\]\[$ERROR_FORMAT\]\h:\w[$exit_code]\[$RESET_FORMAT\]$ " ")'
On Wed, Dec 12, 2018 at 5:49 PM Chet Ramey wrote:
> On 12/12/18 11:36 AM, Valentin Bajrami wrote:
> > While playing around a bit with dot
3d0r4:~$ f=(*)
f3d0r4:~$ (( ${#f[*]} )) || printf '%s\n' "This dir is empty"
f3d0r4:~$ echo "$BASH_VERSION"
4.4.23(1)-release
f3d0r4:~$ cd ../Nonexistingdir
bash: cd: ../Nonexistingdir: No such file or directory
^C
^C
cd Desktop/
f3d0r4:~/Desktop$
--
Met vriendelijke groet,
Valentin Bajrami
_reassemble_comp_words_by_ref: maximum function nesting level
exceeded (4)
++ printf '\033]0;%s@%s:%s\007' root f3d0r4 '~/FOO'
Especially the following line: bash: __reassemble_comp_words_by_ref:
maximum function nesting level exceeded (4)
--
Met vriendelijke groet,
Valentin Bajrami
Hi Mike,
As earlier expained, you are calling foo function recursively. To mitigate
this behaviour you simple set FUNCNEST= foo() { foo; }; foo where N
denotes the number of nested functios to be called.
Op zo 7 okt. 2018 07:57 schreef Mike Gerwitz :
> Hey, Bob!
>
> On Sat, Oct 06, 2018 at 22:4
HI,
While I was testing some variable substitution I came across this error /
unwanted behavior.
So for example:
$ printf '%s' "${/debash: ${/: bad substitution
bash: ${/: bad substitution
just after printf '%s' "${/[TAB] this behavior is triggert.
Is this a bug? Can anyone elaborate this?
Hi,
While looking at indirect reference of variables, typeset seems to support
the -n option. For example
var="value"
typeset -n ref=var
echo "${!ref}"="$ref"
However when running ''help typeset'' I don't see the -n option.
[0][val@laptop:~]$ help typeset
typeset: typeset [-aAfFgilrtux] [-p]
he 'history' builtin
command.
On Wed, Apr 22, 2015 at 10:58 PM, Chet Ramey wrote:
> On 4/21/15 4:30 AM, Valentin Bajrami wrote:
> > The behaviour on bash 4.2.53(1)-release seems to be different. For
> example
> >
> > $ ./history | his
> > bash: his: comm
``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU c...@case.edu
> http://cnswww.cns.cwru.edu/~chet/
>
--
Met vriendelijke groet,
Valentin Bajrami
pecified job
from the jobs list? Is this the behaviour of command_not_found_handle
function?
Thanks!
On Mon, Apr 20, 2015 at 11:13 PM, Chet Ramey wrote:
> On 4/20/15 5:01 PM, Valentin Bajrami wrote:
>
> > Now when running ./history | his where his is not an existing comman
ning twice the output becomes:
$ jobs -l
[1]- 6556 Killed ./history
6557 Stopped (tty input) | his
[2]+ 6830 Stopped (tty input) ./history
6831 | his
I seem not to be able to clean up the jobs.
Can anyone explain what is really happening?
--
Met vriendelijke groet,
Valentin Bajrami
nstead of using a simple loop?
>
> --
> Eduardo Bustamante
> https://dualbus.me/
>
--
Met vriendelijke groet,
Valentin Bajrami
Hi,
According to ''help read'' we can specify -N[chars] to trigger return
automatically. Is it possible to approach read differently?
For example: $re is some regular expression
read -N$re -p "Enter two or three digits to continue " getInput
The above is much of a pseudo-code but I hope you
14 matches
Mail list logo
