l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
August 5: Social gathering
Next Installfest:
TBD
Latest News:
Jul. 4: July, August and September: Security, Photography and Programming for Kids
Page last updated:
2003 Jun 13 12:35

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] readline questions (in bash)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] readline questions (in bash)



--gTtJ75FAzB1T2CN6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Pete,

  I'm interested in seeing what you have for .inputrc

On Fri, Jun 13, 2003 at 12:12:25PM -0500, Jay Strauss wrote:
> I had just gotten through reading those sections before I posted (I should
> have said that).  I could only get it to paste the last thing I cut, not
> multiple back (via M-y scrolling).  I'll keep playing with it
>=20
> Though it seems once i'm in vi -o mode, my C-y and M-y don't work

Jay,

  That is true, they will not work.  The man page documents the defaults
as in emacs mode.

If you switch to vi mode a whole set of things "break" because:
- to do some things like yank you must be in insert mode.
- default key to exit insert mode and switch to command mode is ESC
- on most terminal setups "alt-CHAR" presses map to "ESC" followed by "CHAR"
- the readline library appears to work letter at a time (not=20
  deciding that you readly hitting Meta-CHAR based on the very short
  delay between letters)


  So I think when you hit alt-y to cycle to the next yank readline
sees the ESC and switches you back into command mode, then does
whatever the vi 'y' command does :), instead of moving to the next=20
history element like you wanted... if you rebind yank-pop to something
else like C-O (and you will to use stty to undef flush).  it should
work right.

  If you want to be able to use most of the readline features in vi
mode I suspect you have to remap any commands that use the meta key
modifier into something else and learn your own special binding set=20
(Then reconfigure every machine you use work on with that special=20
binding).

  Hopefully someone knows of a way to get the meta key to work with
libreadline while it is in vi mode... unless that is possible I
recommend not using vi mode if you want the additional readline=20
features.

--=20
GPG key: http://simons-clan.com/~msimons/gpg/msimons.asc
Fingerprint: 524D A726 77CB 62C9 4D56  8109 E10C 249F B7FA ACBE

--gTtJ75FAzB1T2CN6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD4DBQE+6hTN4Qwkn7f6rL4RAseRAJjTTevRJiw9G1dByBgcEZ5EdHzPAKCKBLjP
DQqtXKmr2xtH94n6OgxagQ==
=EnS2
-----END PGP SIGNATURE-----

--gTtJ75FAzB1T2CN6--
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech








LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.