From: "Peter A. Cejchan" <tyapca7@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] documentation suggestion
Date: Tue, 2 Apr 2013 08:34:49 +0200 [thread overview]
Message-ID: <CAM6ozu4=64PyMx3zjBj3A8-Xk0SY1b3K8j17hDoWN+yvfYWeMg@mail.gmail.com> (raw)
In-Reply-To: <CAOCRf5VQcUf1Ly_iFNA6xdV+mBbL8zr0uBHbDuhsEoJqspbx6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
Wow! That's it! I always wanted a 'command window', now I see why it is
needless. Thanks!
On Mon, Apr 1, 2013 at 2:01 PM, Bence Fábián <begnoc@gmail.com> wrote:
> Do what i do. I have only "Edit" on the tagline and write the commands in a
> new window. And just highlight them and 2-1 click on the Edit on the
> window i want the changes to happen. Easier and reusable.
>
>
> 2013/4/1 Peter A. Cejchan <tyapca7@gmail.com>
>
> however, in native Plan9, scrolling goes too fast for multi-line tagline
>> :-)
>> [yes, I know that I should keep commands short, but, e.g., Edit requires
>> newline between commands :((( ]
>>
>> ++pac
>>
>
[-- Attachment #2: Type: text/html, Size: 1421 bytes --]
next prev parent reply other threads:[~2013-04-02 6:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 1:45 trebol
2013-04-01 6:08 ` Peter A. Cejchan
2013-04-01 7:11 ` trebol
2013-04-01 8:24 ` Peter A. Cejchan
2013-04-01 10:51 ` Rudolf Sykora
2013-04-01 12:01 ` Bence Fábián
2013-04-02 6:34 ` Peter A. Cejchan [this message]
2013-04-03 13:11 ` aram
2013-04-03 13:42 ` Bence Fábián
2013-04-04 8:49 ` Mark van Atten
2013-04-04 15:24 ` Rudolf Sykora
2013-04-04 15:46 ` erik quanstrom
2013-04-04 16:03 ` Rudolf Sykora
2013-04-04 16:05 ` Mark van Atten
2013-04-04 16:28 ` Rudolf Sykora
2013-04-04 16:47 ` a
2013-04-05 9:05 ` Mark van Atten
2013-04-05 9:05 ` Mark van Atten
2013-04-05 9:32 ` Mark van Atten
2013-04-05 12:47 ` Mark van Atten
2013-04-08 8:56 ` Mark van Atten
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='CAM6ozu4=64PyMx3zjBj3A8-Xk0SY1b3K8j17hDoWN+yvfYWeMg@mail.gmail.com' \
--to=tyapca7@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).