9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] l8r, etc...
Date: Tue, 19 Oct 2004 15:41:41 +0100	[thread overview]
Message-ID: <437871a70dd36fd98bf26bab33e6549d@vitanuova.com> (raw)
In-Reply-To: <20041018213544.7adfdca2.martin_ml@parvat.com>

> Doesn't adding "l8r" rather defeat the purpose? Like I said, I suspect
> that people who do such things are not typing l8r out of convenience
> (or lazyness), not on modern phones, anyway!

when you're trying to write a philosophical treatise in a text
message, or even giving directions to a party, each of 160 characters
counts for a lot!

personally, when i reach the limit, i go back through the message
removing unnecessary words, deleting excess spaces, and (sometimes)
contracting words (e.g.  you->u, to->2, etc). i don't use "l8r", but
i'm not surprised that some do.

plan 9 relevance? naah, sorry.



      reply	other threads:[~2004-10-19 14:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14  4:16 [9fans] nsf funding research into better (operating) systems geoff
2004-10-14  5:35 ` Ronald G. Minnich
2004-10-14  6:12   ` Kenji Okamoto
2004-10-14  6:57     ` geoff
2004-10-14  7:12       ` Kenji Okamoto
2004-10-14 15:29     ` Ronald G. Minnich
2004-10-14 16:38       ` Dave Lukes
2004-10-15  1:14       ` Kenji Okamoto
2004-10-15  1:55         ` Adrian Tritschler
2004-10-18  4:52           ` Martin C.Atkins
2004-10-18  7:00             ` Skip Tavakkolian
2004-10-18  7:40               ` Martin C.Atkins
2004-10-29  2:01                 ` [9fans] venti i/o error arisawa
2004-10-29  4:37                   ` arisawa
2004-10-18 13:28             ` [9fans] nsf funding research into better (operating) systems boyd, rounin
2004-10-18 16:05               ` [9fans] l8r, etc Martin C.Atkins
2004-10-19 14:41                 ` rog [this message]

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=437871a70dd36fd98bf26bab33e6549d@vitanuova.com \
    --to=rog@vitanuova.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).