9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uvelichitel <uvelichitel@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] New internal command for acme proposal (with implementations)
Date: Fri, 24 Jan 2014 14:49:47 +0200	[thread overview]
Message-ID: <20140124144947218949.528632de@gmail.com> (raw)

Hi dexen.

>> 	Hi 9fans. While working with large sources in acme I feeling some lack
>>of navigation capacity. So two new cmd. 1) 'Rev' , works precisely as
>>'Look' but in reverse direction. It also change behavior of right mouse
>>button search to search reverse. You will notice change with pointer
>>position and little symbol near pipe in tag. Executing 'Look' instantly
>>change behavior back.

>:-/REGEX

Sure, but it regexp search, which more expensive not literal and need
more typing. My proposal as opposite behave exactly as 'Look' and also
change behavior of right mouse
button search.

>> After all navigation 2) 'Tip' , return pointer to
>>last typing point. It understand 2-1 chording, so you can handy insert
>>selection to last insert point without snarfing, including same window.

>Left/Right Arrow keys takes you to the position where selection (cursor)
>currently is.

>if the selection covers several lines, Left takes you to beginning, and
Right
>to the end.


>this plays well with double-click on any open/close
parenthesis/bracket/brace.
>to quickly move to the other end of code block etc.

Proposal 'Tip' command operate with last insertion point, not selection
point, mean 'Tip' cmd return you where you typing after all selections
and scrolling.

Anyway thanks for feedback. Best regards.




             reply	other threads:[~2014-01-24 12:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 12:49 Uvelichitel [this message]
2014-01-24 17:32 ` Bence Fábián
  -- strict thread matches above, loose matches on Subject: below --
2014-01-24 10:44 Uvelichitel
2014-01-24 10:59 ` Uvelichitel
2014-01-24 11:15 ` dexen deVries
2014-02-05 10:49 ` Alexander Sychev
2014-02-05 11:36   ` erik quanstrom
2014-02-05 16:04     ` Bakul Shah
2014-02-05 16:10       ` erik quanstrom
2014-02-05 16:26         ` Bakul Shah
2014-02-05 16:39       ` dexen deVries
2014-02-05 17:04         ` Bakul Shah

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=20140124144947218949.528632de@gmail.com \
    --to=uvelichitel@gmail.com \
    --cc=9fans@9fans.net \
    /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.
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).