zsh-users
 help / color / mirror / code / Atom feed
From: Bernd Steinhauser <linux@bernd-steinhauser.de>
To: zsh-users@zsh.org
Subject: Re: Announcement of Zsh Command Architect v1.0
Date: Sat, 9 Jan 2016 00:16:18 +0100	[thread overview]
Message-ID: <56904342.8020802@bernd-steinhauser.de> (raw)
In-Reply-To: <20160108093313.GA16910@linux.vnet.ibm.com>

Hi,

On 08/01/16 10:33, Dominik Vogt wrote:
>> No more need for a mouse to copy parts of commands in history.
> I never use the mouse for that (partially because the middle mouse
> button is broken):
>
>    (Move cursor to start of word to copy)
>    Ctrl-Space (set mark)
>    (Move cursor to start of word to copy)
>    Ctrl-w (cut)
>    (Move cursor to new location of the word)
>    Ctrl-y (yank; insert cut buffer)
>
> Or with the example from the video:
>
>    # type
>    mplayer -fs
>    # noticed that I need a long word from the history, so comment
>    # out the unfinished command line and store it in the history
>    <ctrl-a>#<return>
>    # look for the history line with the long word; the multi word
>    # search would be helpful
>    <ctrl-r>The_Voi
>    # Mark and cut the file name:
>    <move cursor><ctrl-space><ctrl-f><ctrl-w>
>    # abort editing
>    <ctrl-g>
>    # recall the unfinished command and insert the cut-buffer
>    <cursor-up><ctrl-e> <ctrl-y>
>    # remove comment and execute
>    <ctrl-a><delete><return>
zsh provides a lot of stuff that is really cool and I'm sure that you can do 
pretty much everything out of the box (with using the provided plugins).
However I would have a hard time to remember all of the key shortcuts you're 
using because I don't use emacs.
I know that you can use vi bindings for zle as well, but I'm not really used to 
it and therefore often just fall back to plain mouse select and copy.
Even after 8 years of using zsh, I'm still only scratching the surface of it.

So such a tool as presented for me would be quite cool because it seems to 
provide a quite intuitive approach to edit the command.

Best Regards,
Bernd


  parent reply	other threads:[~2016-01-08 23:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 16:22 Sebastian Gniazdowski
2016-01-08  9:33 ` Dominik Vogt
2016-01-08  9:55   ` Sebastian Gniazdowski
2016-01-08 15:33   ` Sebastian Gniazdowski
2016-01-08 16:29   ` Mikael Magnusson
2016-01-08 17:04     ` Sebastian Gniazdowski
2016-01-09  8:21       ` Sebastian Gniazdowski
2016-01-09 23:54         ` Bart Schaefer
2016-01-10  1:15           ` Mikael Magnusson
2016-01-10  7:32             ` Sebastian Gniazdowski
2016-01-10  9:52               ` Sebastian Gniazdowski
2016-01-10 12:37                 ` Sebastian Gniazdowski
2016-01-10  6:52           ` Sebastian Gniazdowski
2016-01-10  7:20             ` Sebastian Gniazdowski
2016-01-10 19:55               ` history-words (Re: Announcement of Zsh Command Architect v1.0) Bart Schaefer
2016-01-08 23:16   ` Bernd Steinhauser [this message]
2016-01-09  4:24   ` Announcement of Zsh Command Architect v1.0 Bart Schaefer
2016-01-09 17:21 ` jrun
2016-01-10 13:55   ` Sebastian Gniazdowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56904342.8020802@bernd-steinhauser.de \
    --to=linux@bernd-steinhauser.de \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).