The .inputrc doesn't seem to work for me.
I have this in my .inputrc: "\e[3~": delete-char but the delete key is
still a destructive backspace key. Am I doing something wrong?
On 5/6/2020 2:06 AM, David Crayford wrote:
BTW, if you want to use the delete key in the bash command line you
need
On Thu, 7 May 2020 01:02:55 +0800, David Crayford wrote:
>>
>> On 2020-05-06 11:32 PM, Kirk Wolf wrote:
>>> Not so fast: cp and cat are both /bin/sh built-in commands ( documented
>>> under "Built-in commands" in the command reference for sh). So the shell
>>> does employ DDs;-)
>>
>> I didn't know
On 2020-05-07 12:55 AM, David Crayford wrote:
On 2020-05-06 11:32 PM, Kirk Wolf wrote:
Not so fast: cp and cat are both /bin/sh built-in commands ( documented
under "Built-in commands" in the command reference for sh). So the shell
does employ DDs;-)
I didn't know that! I thought they were bi
On 2020-05-06 11:32 PM, Kirk Wolf wrote:
Not so fast: cp and cat are both /bin/sh built-in commands ( documented
under "Built-in commands" in the command reference for sh).So the shell
does employ DDs;-)
I didn't know that! I thought they were binaries in /bin! Thanks ;)
--
On Wed, May 6, 2020 at 9:35 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> >On 2020-05-06 8:31 PM, Kirk Wolf wrote:
> >> cat DD: isn't documented as supported? :-)
> >>
> >> what about "cp //DD:xxx /dev/fd1" - is that the shell?
> >>
> I don't believe shell is clo
On Wed, 6 May 2020 20:40:20 +0800, David Crayford wrote:
>We've had this conversation many times before. Utilities that use
>fopen() support DD:xxx and are not likely to change.
>
>Gil is being pedantic. But maybe IBM should update the doc?
>
Pedantic, yes, but I'd be loath to use in code distri
David,
- using bash interactively and /bin/sh otherwise seems like a reasonable
approach.
(this makes me consider whether the COZBATCH default - to run the user's
login shell - is problematic if this were popular)
- I agree that change bash to use spawn looks extremely hard.
Also, since bash
We've had this conversation many times before. Utilities that use
fopen() support DD:xxx and are not likely to change.
Gil is being pedantic. But maybe IBM should update the doc?
On 2020-05-06 8:31 PM, Kirk Wolf wrote:
cat DD: isn't documented as supported? :-)
what about "cp //DD:xxx /dev/
cat DD: isn't documented as supported? :-)
what about "cp //DD:xxx /dev/fd1" - is that the shell?
On Tue, May 5, 2020 at 3:50 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 5 May 2020 13:12:44 -0500, Kirk Wolf wrote:
> >
> >"deploy" ?
> >
> "employ"?
>
> >
BTW, if you want to use the delete key in the bash command line you need
to put the following line into your readline init file.
echo "\"\e[3~\"": delete-char >> ~/.inputrc
On 2020-05-05 8:11 PM, Michael Babcock wrote:
After reading this thread I finally have my command line completion back!
Agreed. I've got access to she source repository and I don't think spawn
will ever be implemented.
I use bash as a login shell and /bin/sh for scripting and batch. Best of
both worlds.
On 2020-05-05 9:56 PM, Kirk Wolf wrote:
FWIW, I would love to use bash exclusively on z/OS, but without
_B
On Tue, 5 May 2020 13:12:44 -0500, Kirk Wolf wrote:
>
>"deploy" ?
>
"employ"?
>ISTR that this is your favorite example of using DD's in the shell :-)
>
>cat //DD:MYDD
>
o FSVO "favorite". See Appendix K of the Command Ref. It's not
supported; it may work by happenstance; if it breaks you get
Gil,
"deploy" ?
ISTR that this is your favorite example of using DD's in the shell :-)
cat //DD:MYDD
On Tue, May 5, 2020 at 9:17 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote:
>
> >FWIW, I would love to use bas
On Tue, 5 May 2020 08:56:59 -0500, Kirk Wolf wrote:
>FWIW, I would love to use bash exclusively on z/OS, but without
>_BPX_SHAREAS support:
>
>- there are things that you just can't do, like use DDs
>
Where does a shell employ DDs?
>- the overhead for forking new address spaces is significant f
: 616.653.2717
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Gilmartin
Sent: Tuesday, May 5, 2020 9:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AW: Using Windows ssh with z/OS
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from
FWIW, I would love to use bash exclusively on z/OS, but without
_BPX_SHAREAS support:
- there are things that you just can't do, like use DDs
- the overhead for forking new address spaces is significant for many
tasks.
On Tue, May 5, 2020 at 8:06 AM David Crayford wrote:
> To create terminf
On Tue, 5 May 2020 19:32:00 +0800, David Crayford wrote:
>
># switch to bash
>export SHELL=${BASH}
>exec ${BASH} --login
>
Why does that not loop?
Friendlier systems have a "chsh" command.
-- gil
--
For IBM-MAIN subscribe / sig
To create terminfo colors check out Jerry Callens comment in this thread
https://forum.rocketsoftware.com/t/no-colors-running-over-ssh-in-cygwin/1009/7
On 2020-05-05 8:11 PM, Michael Babcock wrote:
After reading this thread I finally have my command line completion back!
I have Rocket’s Bash i
After reading this thread I finally have my command line completion back!
I have Rocket’s Bash installed, set my OMVS segment to the bash shell, used
Bluezone and created a ssh terminal session with VT320, set “disable
dimming colors” and “Use ANSI colors” and set my screen to 32x120. I then
add
On 2020-05-05 6:39 AM, Wendell Lovewell wrote:
Installing Rocket's bash provided the cursor history scrolling I was looking
for.
I don't perceive a difference between TERM=xterm+256color and TERM=xterm in the
command-line-only functions I use. (I don't see any coloring in the ls or
other out
In article <6673472942485742.wa.paulgboulderaim@listserv.ua.edu> you wrote:
> On Mon, 4 May 2020 17:39:39 -0500, Wendell Lovewell wrote:
> >
> >Installing Rocket's bash provided the cursor history scrolling I was looking
> >for.
> >
> >I don't perceive a difference between TERM=xterm+256col
On Mon, 4 May 2020 17:39:39 -0500, Wendell Lovewell wrote:
>
>Installing Rocket's bash provided the cursor history scrolling I was looking
>for.
>
>I don't perceive a difference between TERM=xterm+256color and TERM=xterm in
>the command-line-only functions I use. (I don't see any coloring in
On 5/4/20 4:39 PM, Wendell Lovewell wrote:
I have "bash" as the last line in /etc/profile. This seems to work, but I do have to enter "exit" twice to
close the window. Is there a way to invoke bash so that this is not necessary? I'm also not sure if this matters, but
"echo $SHELL" still show
Thanks to everyone for the advice.
Installing Rocket's bash provided the cursor history scrolling I was looking
for.
I don't perceive a difference between TERM=xterm+256color and TERM=xterm in the
command-line-only functions I use. (I don't see any coloring in the ls or
other output for e
On 5/3/20 11:25 AM, Paul Gilmartin wrote:
Yah, but I wished it had presumed something minimal such as TTY33
until I could EXPORT TERM and/or set TERMINFO.
Put it in your .profile or .bash_profile or whatever.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.we
The thing I REALY miss in OMVS is command line completion with TAB key.
On Sun, May 3, 2020 at 12:25 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote:
> >
> >> But z/OS used to deny login when TERM was not in term
On Sat, 2 May 2020 12:02:56 -0600, Jack J. Woehr wrote:
>
>> But z/OS used to deny login when TERM was not in terminfo.
>> Did it ever get better?
>
>If it denies login to that term setting, you try something else :)
>
Yah, but I wished it had presumed something minimal such as TTY33
until I coul
Jack,
Not everyone learns that way , I have ADHD and the way you described is the
way I must learn, because of the sometimes levels of my attention.
Scott
On Sun, May 3, 2020 at 12:50 PM scott Ford wrote:
> Wendell,
>
> Contact me of listserv I can help you out, we been using x3270 with their
Wendell,
Contact me of listserv I can help you out, we been using x3270 with their
scripting to this sort of thing for awhile, including CI/CD type work.
Scott
On Sun, May 3, 2020 at 3:30 AM Jack J. Woehr wrote:
> On 5/2/20 11:16 AM, Paul Gilmartin wrote:
> > Doesn't ssh supposed to set that u
On 5/2/20 11:16 AM, Paul Gilmartin wrote:
Doesn't ssh supposed to set that up? But z/OS may not
be savvy to the OP's TERM. Is it in terminfo?
I dunno, but it sure works better than xterm-color256 on IBM i so just
guessing.
But z/OS used to deny login when TERM was not in terminfo.
Did it
On Sat, 2 May 2020 10:51:01 -0600, Jack J. Woehr wrote:
>On 5/2/20 9:53 AM, Wendell Lovewell wrote:
>> When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle
>> keys the same way Ubuntu does. I have these settings:
>>
>> echo $TERM displays xterm-color256
>> echo $SHELL display
On 5/2/20 9:53 AM, Wendell Lovewell wrote:
When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle keys
the same way Ubuntu does. I have these settings:
echo $TERM displays xterm-color256
echo $SHELL displays /bin/sh
As Gil pointed out, run bash. It's often there somewhere.
> >
> >Best regards
> >Mike
> >
> >-Urspr??ngliche Nachricht-
> >Von: IBM Mainframe Discussion List Im Auftrag von
> >Wendell Lovewell
> >Gesendet: Saturday, May 02, 2020 17:54
> >An: IBM-MAIN@LISTSERV.UA.EDU
> >Betreff: Using Windows ssh wit
t Im Auftrag von
>Wendell Lovewell
>Gesendet: Saturday, May 02, 2020 17:54
>An: IBM-MAIN@LISTSERV.UA.EDU
>Betreff: Using Windows ssh with z/OS
>
>When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle keys
>the same way Ubuntu does. I have these setting
@LISTSERV.UA.EDU
Betreff: Using Windows ssh with z/OS
When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle keys
the same way Ubuntu does. I have these settings:
echo $TERM displays xterm-color256
echo $SHELL displays /bin/sh
Specifically, I'd like:
a) The cursor-up key
When connecting to z/OS (USS) using ssh, I'd like the USS shell to handle keys
the same way Ubuntu does. I have these settings:
echo $TERM displays xterm-color256
echo $SHELL displays /bin/sh
Specifically, I'd like:
a) The cursor-up key to perform the "history-search-backward" function
b) The c
36 matches
Mail list logo