The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Don Hopkins <don@donhopkins.com>
To: "Sijmen J. Mulder" <ik@sjmulder.nl>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] TUHS Digest, Vol 33, Issue 7
Date: Wed, 8 Aug 2018 14:59:06 +0200	[thread overview]
Message-ID: <6EBCF9E5-4600-42D6-9F83-3E2966140540@donhopkins.com> (raw)
In-Reply-To: <20180808123229.86FD5E465F@mailuser.nyi.internal>

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

I strongly dislike something as trivial as a prompt taking up my TIME and ATTENTION. I have room for many more lines in my terminal emulator and emacs shell window than I have time and attention or patience for carefully pointing and clicking and editing out prompts (or even talking about half-assed kludges when there’s a simple obvious solution to the problem), and much better things to do with my time and energy. 

To me, there is virtually no cost to having an extra line in my terminal or shell window, while the repeated cost of all the time and effort I have to waste working around the clutter of the prompt, integrated over the hundreds of times per day I use the command line, totally overwhelms any aesthetic considerations of disliking prompts taking up a line (or insisting on a clear line before it -- I don’t understand why you would suggest such a straw man, which is not what I was advocating). I’m not trying to paint the Mona Lisa in ASCII art, I’m simply trying to save time and effort. 

What’s the downside to the prompt taking up a full line (and as a result, the command taking up a whole line without being polluted with a prompt), other than strongly disliking things you’re not used to? Is your terminal emulator configured to only remember 24 lines? And why are you so averse to clutter, yet have no problem with the prompt cluttering up your input, which causes real non-aesthetic problems? 

I used to use a shitty HP 2640 terminal in high school that only had a half a page of screen memory (but didn’t store the spaces at the end of the lines, so you could fit 12 80-character lines on the screen, or 24 40-character lines), so if you printed out long lines, it would start scrolling before there was a full screen of text. At least the 300 baud modem gave you time to ponder over those few lines before they scrolled off the screen. In that scenario, lines of text were precious, although the HP terminals charge by characters, not lines. But I don’t think anybody in their right mind uses terminals like that any more. 

-Don


> On 8 Aug 2018, at 14:32, Sijmen J. Mulder <ik@sjmulder.nl> wrote:
> 
> > Decades ago I made my prompt simply end with a newline, which perfectly
> > and cleanly solves the problem of making it easy to copy and paste a
> > whole line
>  
> I never considered setting a copy/paste-friendly prompt but I strongly
> dislike prompts taking up a line. Admittedly it's nice to have some room
> for extra information but then you'll want a clear line above it too for
> visual structure and that's all just too much clutter for me.


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

  reply	other threads:[~2018-08-08 12:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1533693601.12251.tuhs@minnie.tuhs.org>
2018-08-08 12:10 ` Don Hopkins
2018-08-08 12:32   ` Sijmen J. Mulder
2018-08-08 12:59     ` Don Hopkins [this message]
2018-08-08 13:51       ` Sijmen J. Mulder
2018-08-08 14:45         ` Clem Cole
2018-08-08 14:56           ` Lawrence Stewart
2018-08-08 15:09           ` [TUHS] the distinct smell of light machine oil, was " Toby Thain
2018-08-08 17:38             ` Cornelius Keck
2018-08-08 19:14               ` Jim Geist
2018-08-08 20:44                 ` Warner Losh
2018-08-09  5:14                   ` arnold
2018-08-09  5:55                     ` Jim Geist
2018-08-09  6:02                       ` George Michaelson
2018-08-09  7:20                       ` Dave Horsfall
2018-08-09 12:36                       ` Warner Losh
2018-08-09 13:45                         ` Michael Parson
2018-08-09 13:31                   ` Clem Cole
2018-08-09 14:15                     ` Derek Fawcus
2018-08-09 14:26                       ` Eric Wayte
2018-08-10 11:37                         ` Pete Turnbull
2018-08-10 11:37                       ` Pete Turnbull
2018-08-10 16:24                         ` Tom Ivar Helbekkmo via TUHS
2018-08-10 16:58                           ` Pete Turnbull

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=6EBCF9E5-4600-42D6-9F83-3E2966140540@donhopkins.com \
    --to=don@donhopkins.com \
    --cc=ik@sjmulder.nl \
    --cc=tuhs@minnie.tuhs.org \
    /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).