|
Grex > Coop7 > #108: Possible Modifications to "mail" Default Behavior | |
|
| Author |
Message |
| 25 new of 95 responses total. |
n8nxf
|
|
response 25 of 95:
| 
Oct 10 15:06 UTC 1995 |
How about "Copy to:"?
|
selena
|
|
response 26 of 95:
|
Oct 10 18:25 UTC 1995 |
Well, if you have to, how about Cc: (send copy to<return for none>):
That way, you educate, too.
|
steve
|
|
response 27 of 95:
|
Oct 11 00:03 UTC 1995 |
Thats what I'd like to see: a slightly smarter mail that can ask
the user about things like that.
|
selena
|
|
response 28 of 95:
|
Oct 11 04:25 UTC 1995 |
<STeve liked an idea of mine! Write it down on your calendars! ;} >
|
sidhe
|
|
response 29 of 95:
|
Oct 11 16:00 UTC 1995 |
I do not like the idea of trimming the headers. The information
there is useful sometimes, and was no problem getting used to when I
was a newbie.
|
ajax
|
|
response 30 of 95:
|
Oct 11 17:12 UTC 1995 |
Is there a way to show headers trimmed by default, but to display fuller
headers to users who want them? I can see where "Message-ID" *could* be
useful, but I'd be none the worse for never having seen one. :-)
|
janc
|
|
response 31 of 95:
|
Oct 11 18:56 UTC 1995 |
Type "P" instead of "p" to print the message and every fool header will
be displayed.
|
janc
|
|
response 32 of 95:
|
Oct 11 19:00 UTC 1995 |
And remember...any user can override *all* the changes suggested here
with a few lines in his .mailrc file.
The argument is not that these are better settings for *everyone*. Anyone
who uses mail a lot will certainly want to set his preferences. The argument
is that these are better defaults for newusers.
|
ajax
|
|
response 33 of 95:
|
Oct 11 21:01 UTC 1995 |
That's what I was wondering. I can't see a reason for such lengthy
headers by default then.
|
selena
|
|
response 34 of 95:
|
Oct 12 20:52 UTC 1995 |
I don't get the problem.
When I was new, I just ignored the gobblety-gook, and read the letter
below it. It was cool.
|
janc
|
|
response 35 of 95:
|
Oct 12 22:15 UTC 1995 |
It's not a big problem. I wouldn't bother if there weren't other things
worth fixing. It's just nicer not to spill gobblty gook all over people's
screens.
|
scott
|
|
response 36 of 95:
|
Oct 13 00:28 UTC 1995 |
I hate it when people bitch about how things should be easier and then
get upset shen things changes.
|
selena
|
|
response 37 of 95:
|
Oct 13 03:03 UTC 1995 |
Well, yeah.. your point?
|
lilmo
|
|
response 38 of 95:
|
Oct 13 03:52 UTC 1995 |
> It's just nicer not to spill gobblty gook all over people's screens.
Yeah, it's so messy to clean up. :-)
|
mlady
|
|
response 39 of 95:
|
Oct 13 19:35 UTC 1995 |
It's not broke.. don't fix it.
|
ajax
|
|
response 40 of 95:
|
Oct 13 21:50 UTC 1995 |
Re Selena/Mlady, I wouldn't say it's a problem, or that it's broken;
this is just a suggested improvement. I'm sure "if it ain't broke,
don't fix it" has been the death-motto of more than one organization!
It's an interesting contrast to the Japanese "kaizen" process of
continual improvements, which yields sub-atomic Sony Walkmans. :-)
|
janc
|
|
response 41 of 95:
|
Oct 14 01:31 UTC 1995 |
It's been my experience on these systems that there is always a constituency
for the status quo.
|
davel
|
|
response 42 of 95:
|
Oct 14 12:53 UTC 1995 |
Um, that's *one* way of putting it.
|
wisdom
|
|
response 43 of 95:
|
Oct 14 21:39 UTC 1995 |
Well, the status quo hasn't really hurt anything has it?
In this case, I mean. If it has, then, by all menas. do something!
|
ajax
|
|
response 44 of 95:
|
Oct 14 22:20 UTC 1995 |
AAAAaaaaaaiiiiiiiiieeeeeeeee!!!!!!!!!
<Thunk thunk thunk> (head against monitor :-).
|
adbarr
|
|
response 45 of 95:
|
Oct 14 23:00 UTC 1995 |
<tippy toe, tippy toe out of the room>
|
janc
|
|
response 46 of 95:
|
Oct 15 02:06 UTC 1995 |
The status quo does hurt people. Not a lot of people. But the status quo
didn't hurt a lot of people three years ago either. Maybe we should have
stopped then. What was it? Sun 2, three phone lines, no real internet?
|
remmers
|
|
response 47 of 95:
|
Oct 15 10:54 UTC 1995 |
When deciding between the status quo and some alternative that has
come up, sometimes the best choice is the alternative, other times
it's the status quo. You have to decide each case on its own merits.
(By the way, three years ago it was Sun-2, five phone lines, no real
internet.)
|
lilmo
|
|
response 48 of 95:
|
Oct 15 21:43 UTC 1995 |
Re #45: I think that you made the right choice, for once, adbarr. :-)
Re #43: I 'd rather not wait until it is a big problem to solve it. "An
ounce of prevention is worth a pound of cure."
|
selena
|
|
response 49 of 95:
|
Oct 15 22:58 UTC 1995 |
Wel, I'd like to know if it's even a small one.
|