Hi Jude,
On 9/7/18 4:09 PM, Jude DaShiell wrote:
> Try putting a -n switch on that echo command and I predict this problem
> will go away.
I am sorry, but adding the »-n« switch did not solve that problem. It is
exactly the same behavior.
Cheers,
Norbert
--
On 9/8/18 4:28 PM, Curt wrote:
> On 2018-09-08, Stefan Krusche wrote:
>> Am Samstag, 8. September 2018 schrieb Stefan Krusche:
>>> Thanks for food for thought, David. The question why, and where exactly,
>>> the different behaviour emerges, remains unanswered for me. It would be
>>> interesting to
Hi,
i wrote:
> That's probably because there is bash-ism in the script,
Of course i meant to say:
That's probably because there is _no_ bash-ism in the script,
Have a nice day :)
Thomas
Hi,
David Wright wrote:
> As I posted, I get the same behaviour whichever shebang I have,
> any of bash|dash|sh.
That's probably because there is bash-ism in the script, except the
variable READLINE_LINE which the boss bash is supposed to have set.
> If the script has no shebang, then (I assume
On 2018-09-08, Stefan Krusche wrote:
> Am Samstag, 8. September 2018 schrieb Stefan Krusche:
>> Thanks for food for thought, David. The question why, and where exactly,
>> the different behaviour emerges, remains unanswered for me. It would be
>> interesting to know how the OP actually solved his
Am Samstag, 8. September 2018 schrieb Stefan Krusche:
> Thanks for food for thought, David. The question why, and where exactly,
> the different behaviour emerges, remains unanswered for me. It would be
> interesting to know how the OP actually solved his problem.
Just read it: OP *inserted* said
Am Freitag, 7. September 2018 schrieb David Wright:
> On Fri 07 Sep 2018 at 18:40:51 (+0200), Stefan Krusche wrote:
> > > With a shebang, the parent process of the script is reported as
> > > /bin/dash /home/david/bin/_bash_man
> > > (and the shell corresponds to the dash|bash|sh shebang).
> > >
On Fri 07 Sep 2018 at 18:40:51 (+0200), Stefan Krusche wrote:
> Am Freitag, 7. September 2018 schrieb David Wright:
> > On Fri 07 Sep 2018 at 14:58:48 (+0200), Stefan Krusche wrote:
> > > Am Freitag, 7. September 2018 schrieb Norbert Gruener:
> > > > Hi Stefan,
> > > >
> > > > >> bash^[[D^[[C^[[
Am Freitag, 7. September 2018 schrieb David Wright:
> On Fri 07 Sep 2018 at 14:58:48 (+0200), Stefan Krusche wrote:
> > Am Freitag, 7. September 2018 schrieb Norbert Gruener:
> > > Hi Stefan,
> > >
> > > >> bash^[[D^[[C^[[B^[[A
> > > >
> > > > This reminds me of programs (ed, rcs, telnet etc.) w
On 2018-09-07 11:07, Stefan Krusche wrote:
Hallo Norbert,
Am Donnerstag, 6. September 2018 schrieb Norbert Gruener:
Hi all,
In my Bash shell (».bashrc«) I have »bind« a command to the »F1« key
bind -x '"\eOP":"_bash_man"'# F1 man
The script »_bash_man« looks like (it is simplifie
On Fri 07 Sep 2018 at 14:58:48 (+0200), Stefan Krusche wrote:
> Am Freitag, 7. September 2018 schrieb Norbert Gruener:
> > Hi Stefan,
> >
> > >> bash^[[D^[[C^[[B^[[A
> > >
> > > This reminds me of programs (ed, rcs, telnet etc.) which don't use
> > > readline and have less command line editing c
Try putting a -n switch on that echo command and I predict this problem
will go away.
On Thu, 6 Sep 2018, Norbert Gruener wrote:
> Date: Thu, 6 Sep 2018 11:38:10
> From: Norbert Gruener
> To: debianUsers
> Subject: Bash-Problem with cursor position after calling a f
Am Freitag, 7. September 2018 schrieb Norbert Gruener:
> Hi Stefan,
>
> you made my day!!! :-))
Nice. :-)
Kind regards,
Stefan
PS: no need to CC me, I'm subscribed ;-)
Hi Stefan,
you made my day!!! :-))
On 9/7/18 2:58 PM, Stefan Krusche wrote:
>
> Maybe, just maybe... ;-) the cause lies in what you use as a shebang in your
> script. If I do:
> $ sh
> I get a dash subshell on my system which has apparently no command line
> editing
> with readline configured
Am Freitag, 7. September 2018 schrieb Norbert Gruener:
> Hi Stefan,
>
> >> bash^[[D^[[C^[[B^[[A
> >
> > This reminds me of programs (ed, rcs, telnet etc.) which don't use
> > readline and have less command line editing capabilities. Backspace
> > should work, though.
>
> It is exactly my impress
Hi Stefan,
On 9/7/18 12:07 PM, Stefan Krusche wrote:
> Hallo Norbert,
>
> Am Donnerstag, 6. September 2018 schrieb Norbert Gruener:
>> Hi all,
>>
>> In my Bash shell (».bashrc«) I have »bind« a command to the »F1« key
>>bind -x '"\eOP":"_bash_man"'# F1 man
>>
>> The script »_bash_man
Hallo Norbert,
Am Donnerstag, 6. September 2018 schrieb Norbert Gruener:
> Hi all,
>
> In my Bash shell (».bashrc«) I have »bind« a command to the »F1« key
>bind -x '"\eOP":"_bash_man"'# F1 man
>
> The script »_bash_man« looks like (it is simplified only for test reasons)
>
>echo
Hi Thomas,
On 9/6/18 8:30 PM, Thomas Schmitt wrote:
> Hi,
>
> Norbert Gruener wrote:
>> after my upgrade to Stretch I got these problems :-(
>
> Did you already check whether it is a matter of the terminal program ?
> If it is a bit rot problem between readline and terminal, then you
> might g
Hi,
Norbert Gruener wrote:
> after my upgrade to Stretch I got these problems :-(
Did you already check whether it is a matter of the terminal program ?
If it is a bit rot problem between readline and terminal, then you
might get lucky with a different one.
Have a nice day :)
Thomas
Hi Thomas,
On 9/6/18 6:28 PM, Thomas Schmitt wrote:
> Hi,
>
> i replayed this on Jessie.
under Jessie this was working for me too. But after my upgrade to
Stretch I got these problems :-(
Cheers,
Norbert
--
Hi,
i replayed this on Jessie.
I get printed lines "aaa" for every F1 i press.
No shell prompts get printed inbetween, but rather the shell prompt
and the text "aaa" stay in the base line of the xterm.
The text "aaa" can be edited and the new text gets printed with F1.
Like after three times pres
Hi all,
In my Bash shell (».bashrc«) I have »bind« a command to the »F1« key
bind -x '"\eOP":"_bash_man"'# F1 man
The script »_bash_man« looks like (it is simplified only for test reasons)
echo "${READLINE_LINE}"
When I type »aaa« and then press »F1«, I see a new line on the sc
On 12/13/06, Almut Behrens <[EMAIL PROTECTED]> wrote:
> In other words subshell expand willcard `*' and shows all files into
> directory!
You need to put double quotes around the variable when echoing it:
echo "$SUBJECT"
Sure! Dummies error. Sorry.
--
Openclose.it - Idee per il software libe
On Wed, 13 Dec 2006 12:10:58 +0100, Andrea Ganduglia wrote:
> Hi. I'm working on Sarge. I'm parsing a text file when..
>
> cd tmp
> ls
> aaa bbb ccc ddd
>
> My script parse all file into directory, and grep ^Subject line.
>
> for i in *; do
> egrep '^Subject:' $i
> done
>
> Subject: Hello Andre
Hi. I'm working on Sarge. I'm parsing a text file when..
cd tmp
ls
aaa bbb ccc ddd
My script parse all file into directory, and grep ^Subject line.
for i in *; do
egrep '^Subject:' $i
done
Subject: Hello Andrea
Subject: Ciao Debiam
Subject: {SpAm?} * Viiagrra * Ciialiis * Leevittra *
Subject:
On Mon, 23 Jun 2003 23:48:10 +0100
Colin Watson <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 23, 2003 at 03:37:43PM -0500, matt zagrabelny wrote:
> > On Mon, 2003-06-23 at 13:57, David selby wrote:
> > > If this is the case, how can I test a string ?
> >
> > for your enjoyment:
> >
> > #!/bin/bash
>
On Tue, June 24 at 8:03 AM EDT
David selby <[EMAIL PROTECTED]> wrote:
> Colin Watson wrote:
>
> >On Mon, Jun 23, 2003 at 07:57:07PM +0100, David selby wrote:
> >
> >
> >>My bash masterpeice is almost complete ... I have one last problem
> >that >no matter how many "" or '' I use I cannot get a
Colin Watson wrote:
On Mon, Jun 23, 2003 at 07:57:07PM +0100, David selby wrote:
My bash masterpeice is almost complete ... I have one last problem that
no matter how many "" or '' I use I cannot get around.
I need to use an if...then construct to check that my 4 digit date field
is 4 numeri
On Mon, Jun 23, 2003 at 07:57:07PM +0100, David selby wrote:
> My bash masterpeice is almost complete ... I have one last problem that
> no matter how many "" or '' I use I cannot get around.
>
> I need to use an if...then construct to check that my 4 digit date field
> is 4 numerical digits.Thi
On Mon, Jun 23, 2003 at 03:37:43PM -0500, matt zagrabelny wrote:
> On Mon, 2003-06-23 at 13:57, David selby wrote:
> > If this is the case, how can I test a string ?
>
> for your enjoyment:
>
> #!/bin/bash
>
> if echo $fourdig | grep ^[0-9]*$ > /dev/null 2>&1; then
That *really* needs some quo
On Mon, 2003-06-23 at 13:57, David selby wrote:
> My bash masterpeice is almost complete ... I have one last problem that
> no matter how many "" or '' I use I cannot get around.
>
> I need to use an if...then construct to check that my 4 digit date field
> is 4 numerical digits.This is for erro
My bash masterpeice is almost complete ... I have one last problem that
no matter how many "" or '' I use I cannot get around.
I need to use an if...then construct to check that my 4 digit date field
is 4 numerical digits.This is for error checking. I thought [sets] was
the way to go
if
On Wed, 02 Aug 2000 13:51:22 PDT, "Sean 'Shaleh' Perry" writes:
>>
>> Q: Can I just go and install a user with the same UID/GID as root, but
>> /bin/tcsh as login-shell, so I have a fallback, JIC?
>>
>better yet, set root's shell to something like sash.
ah, perfectly ;-) "statically linked" "bu
>
> Q: Can I just go and install a user with the same UID/GID as root, but
> /bin/tcsh as login-shell, so I have a fallback, JIC?
>
better yet, set root's shell to something like sash.
[Disclaimer: don´t waste your time reading if you´re not really
interested, the "problem" is gone for now, and I´m just trying to find
out what could have caused it.]
---
malloc: block on free list clobbered
last command: (null)
Report this to [EMAIL PROTECTED]
---
here we go...
I´m unsure if
Well, my mirror appears to have stopped updating about a week ago, so when
I told a few machines to do an apt-get dist-upgrade they all barfed on the
broken bash package. (The mirror had not upgraded my local copy to the
fixed bash package...)
Is there any easy way to recover these things withou
I had a similar problem on a Redhat 5.1 system once. I was unable to
login locally or remotely as anything but root. It ended up I had a
file called nologin in my /etc/ directory, once I removed this I could
login. But this sounds like it is a problem more related to your system
not finding a re
Hi,
I just did a partial upgrade to slink - partial because of limited
bandwidth - and now I cannot use telnet or ssh to my box. After
entering the password I get:-
Linux elm 2.1.126 #4 Wed Oct 28 19:37:29 WST 1998 i586 unknown
Last login: Sun Nov 8 13:13:40 on ttyp0 from elm.cbcfreo.wa.edu.au
I just want to thank all of the people who were very quick and helpful in
dealings with my broken upgrade of the hamm-based bash package (2.01.1-1).
I have managed to install ash package, edit /etc/passwd to make ash a login
shell for root and user, and than reinstall old, working bash_2.01-5.deb
39 matches
Mail list logo
