unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: 1L?
Date: Wed, 06 Feb 2019 17:50:57 +0100	[thread overview]
Message-ID: <86va1w7te6.fsf@zoho.eu> (raw)
In-Reply-To: jwv1s4k98vi.fsf-monnier+emacs@gnu.org

Stefan Monnier wrote:

>> I am unfamiliar with the term "1L", and
>> Google wasn't much help. What does it mean
>> beyond "one liter"?
>
> I think he meant just that: one liter, i.e.
> an approximate upper limit on the size of
> the machine.

Shouldn't *all* "1L machines" run Emacs
just fine?

I have an RPi3 from 2015 and it runs Emacs as
I'm typing this, and not only Emacs but the
familiar Raspbian OS, which is "Debian for the
RPi", but not exactly the real McCoy, so for
really exotic projects, I'd recommend a vanilla
Debian box with all the fixings.

Anyway the RPi, even including the case, should
be way below the 1L constraint so I'd expect
any machine significantly bigger that that to
at the very least run or favorite editor/OS
with no problems.

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2019-02-06 16:50 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  2:05 Suggestions for 1L computer to run Emacs 2019 Van L
2019-02-03 13:21 ` Stefan Monnier
2019-02-05  1:00   ` Van L
2019-02-06 15:06     ` Stefan Monnier
2019-02-09  1:58       ` Van L
2019-02-09  3:07         ` Emanuel Berg
2019-02-11 13:18           ` Van L
2019-02-11 20:31             ` Emanuel Berg
2019-02-12 12:37               ` [*OFF-TOPIC*] " Van L
2019-02-09 13:28         ` Stefan Monnier
2019-02-09 20:29           ` Emanuel Berg
2019-02-10 14:54             ` [OFFTOPIC] " Stefan Monnier
2019-02-10 15:03               ` 조성빈
2019-02-10 18:14                 ` Stefan Monnier
2019-02-10 20:26               ` Emanuel Berg
2019-02-06 15:38 ` 1L? (was: Suggestions for 1L computer to run Emacs 2019) Skip Montanaro
2019-02-06 16:31   ` 1L? Stefan Monnier
2019-02-06 16:50     ` Emanuel Berg [this message]
2019-02-07 10:31     ` 1L? Van L
2019-02-07 10:58       ` 1L? 조성빈
2019-02-07 15:47         ` 1L? Emanuel Berg
2019-02-07 16:38           ` 1L? 조성빈
2019-02-07 19:51             ` 1L? Emanuel Berg
2019-02-08  2:27               ` 1L? 조성빈
2019-02-08 15:02                 ` 1L? Emanuel Berg
2019-02-08  6:16           ` 1L? Vladimir Sedach
2019-02-08 22:55             ` 1L? Emanuel Berg
2019-02-08  8:46         ` 1L? Van L
2019-02-08 15:03           ` 1L? Emanuel Berg
2019-02-07 15:42       ` 1L? Emanuel Berg
2019-02-08  9:14         ` 1L? Van L
2019-02-08  9:27           ` 1L? tomas
2019-02-08 15:15             ` 1L? Emanuel Berg
2019-02-08 15:39               ` 1L? tomas
2019-02-10  6:34             ` 1L? Van L
2019-02-10  8:11               ` 1L? tomas
2019-02-10 20:24                 ` 1L? Emanuel Berg
2019-02-10 20:21               ` 1L? Emanuel Berg
2019-02-08 15:10           ` 1L? Stefan Monnier
2019-02-08 15:10           ` 1L? Emanuel Berg
2019-02-10 15:02           ` [OFFTOPIC] 1L? Stefan Monnier
2019-02-10 15:34             ` Richard Melville
2019-02-11 19:48               ` Stefan Monnier
2019-02-12  3:48                 ` Vladimir Sedach
2019-02-10 20:27             ` Emanuel Berg
2019-02-12  4:31               ` Xavier Maillard
2019-02-12  5:19                 ` Emanuel Berg
2019-02-14 11:10                   ` Van L
2019-02-15 18:49                   ` Xavier Maillard
2019-02-12 18:35             ` Steinar Bang
2019-02-12 22:23               ` Emanuel Berg
2019-02-13 20:34               ` Stefan Monnier
2019-02-14  8:34                 ` tomas
2019-02-16  7:58                 ` Steinar Bang
2019-02-08 15:07         ` 1L? Stefan Monnier
2019-02-15 10:06           ` 1L? Van L

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86va1w7te6.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).