9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jimr@highwire.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Musings on Interfaces
Date: Thu,  1 Sep 2016 10:20:39 -0700	[thread overview]
Message-ID: <CAPd04b77Q+xBy9XtbOwG-Hmu_gL4cr6kRYxGDktmSYGiKr+ejg@mail.gmail.com> (raw)
In-Reply-To: <CALAsyW00DugfoW+ZjS6ks8jM375Qjui8Y2QF=5p3_ODw_9gb=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

On Thu, Sep 1, 2016 at 9:05 AM, Mark van Atten <vanattenmark@gmail.com>
wrote:

> The one regret I have about sam is that it doesn't do scroll-select. I
> write papers rather than programs, and often want to select and
> quickly move around large chunks of text whose boundaries are usually
> not marked syntactically, even though I use LaTeX.


​So you couldn't do something like clicking on the start and typing in a
.,/<pattern>/ where <pattern> holds the last few words of the text range
you wanted to select?  I understand not having regular markup like a
program, but if a few words could be used to identify the end point I would
have assumed you could use that?

Jim

[-- Attachment #2: Type: text/html, Size: 1630 bytes --]

  reply	other threads:[~2016-09-01 17:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 14:42 Brantley Coile
2016-09-01 15:40 ` Bakul Shah
2016-09-01 16:05   ` Mark van Atten
2016-09-01 17:20     ` James A. Robinson [this message]
2016-09-01 19:10       ` Mark van Atten
2016-09-01 22:15         ` Travis Moore
2016-09-01 15:59 ` James A. Robinson
2016-09-01 16:36 ` Adriano Verardo
2016-09-01 17:54   ` Brantley Coile
2016-09-01 18:05     ` arnold
2016-09-01 22:56 ` Winston Kodogo
2016-09-02  1:52   ` Winston Kodogo
2016-09-02  9:06     ` cinap_lenrek
2016-09-02 14:19       ` Steven Stallion
2016-09-02 15:37         ` Kurt H Maier
2016-09-02  6:10   ` Mart Zirnask
2016-09-02  7:34   ` Steve Simon
2016-09-02  7:59     ` Ole-Hjalmar Kristensen

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=CAPd04b77Q+xBy9XtbOwG-Hmu_gL4cr6kRYxGDktmSYGiKr+ejg@mail.gmail.com \
    --to=jimr@highwire.org \
    --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).