From: erik quanstrom <quanstro@quanstro.net>
To: jimr@highwire.stanford.edu, 9fans@9fans.net
Subject: Re: [9fans] Acme win and 75+ character Send commands
Date: Thu, 5 Sep 2013 18:13:49 -0400 [thread overview]
Message-ID: <75c24d38552c58790951a3be14d2805c@ladd.quanstro.net> (raw)
In-Reply-To: <CAPd04b67G9dRsRfGKFh0RrF4UGce3xXy6cXwB08SCfe=X282yQ@mail.gmail.com>
On Thu Sep 5 16:19:19 EDT 2013, jimr@highwire.stanford.edu wrote:
> D'oh, I'm thinking maybe it's bash that is doing
> this (since bash is my default shell instead of
> rc).
it's likely readline, which has an 80-column mind.
- erik
next prev parent reply other threads:[~2013-09-05 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:16 James A. Robinson
2013-09-05 20:17 ` James A. Robinson
2013-09-05 22:13 ` erik quanstrom [this message]
2013-09-06 0:30 ` Rob Pike
2013-09-06 3:06 ` James A. Robinson
2013-09-06 4:10 ` Rob Pike
2013-09-06 5:23 ` Bruce Ellis
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=75c24d38552c58790951a3be14d2805c@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=jimr@highwire.stanford.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).