9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gabriel Diaz <gabidiaz@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] p9p: SAM snarf with X
Date: Sun, 28 Aug 2005 11:04:18 +0100	[thread overview]
Message-ID: <82c890d0050828030412edbb16@mail.gmail.com> (raw)
In-Reply-To: <W1701212174521125201308@webmail2>

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

Hi
 I would love to have an -r like option in acme. Then i will use acme all 
the time. 
 Acme is nice when you can mount all you need, but sam is nicer when you 
must do a -r to edit files :).
  gabi

 2005/8/28, quanstro@speakeasy.net <quanstro@speakeasy.net>: 
> 
> would it be utter sacrilege and or a complete waste of time
> to add some acme features to samterm like:
> 
> 1. sharing the snarf buffer with the window system.
> 2. cording
> 
> i've been thinking about this for a while, but haven't gotten
> to it.
> 
> maybe the answer is "use acme, then". but often i want sam.
> it's a lot easier to do some complicated, scripted editing
> with sam than anything else. i like having a terminal-like
> window for editing.
> 
> but since i use acme most of the time, i really grind the
> mental gears switching back.
> 
> maybe what i want is (warning: this idea is half baked)
> editing stripped out of acme and sam run in windows that
> contain files.
> 
> btw, this command with acme
> 
> x:0x....: |tr 'A-Z' 'a-z'
> 
> gave me "addresses out of order". sam was happy with it.
> the text i had selected was like this:
> 
> {0x00AA, 0x00AA, "whatever",},
> {0x00BB, 0x00BB, "whatever2",},
> 
> erik
> 
> 
> 
>

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

  reply	other threads:[~2005-08-28 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28  3:55 quanstro
2005-08-28 10:04 ` Gabriel Diaz [this message]
2005-08-29  0:36 ` Russ Cox
2005-08-29 13:18   ` Richard Bilson
  -- strict thread matches above, loose matches on Subject: below --
2005-08-28 10:22 Steve Simon
2005-08-26 14:05 Gabriel Diaz
2005-08-26 14:19 ` Russ Cox
2005-08-26 15:01   ` Gabriel Diaz

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=82c890d0050828030412edbb16@mail.gmail.com \
    --to=gabidiaz@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).