From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Not a timetable
Date: 17 Aug 1998 14:53:53 +0200 [thread overview]
Message-ID: <kigemufydjx.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stainless Steel Rat's message of "14 Aug 1998 16:17:02 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> FP> This is a bit like if I was saying that I do not use colourisation of
> FP> articles in Gnus, and intend to refuse to install or use Gnus until
> FP> there is an option to produce `.elc' files with all colourisation code
> FP> removed. Is that it? Is there anything else to it?
>
> Well, no. If you wanted to, removing the color-setting code is easilly
> doable: changing the default color setting code to use copy-face a lot is
> the easiest way I can think of to do it. Hacking custom to think you
> always have a monochrome display is another (and is, in fact, my personal
> favorite :).
Neither of these "remove" the code -- they just disable its execution.
So I don't understand the difference between these hacks and `export
EMACS_UNIBYTE=1' which disables MULE.
> MULE is different. Even "disabled" it is still there, looming in the
> background, consuming resources that could be used for something useful
> (for whatever definition of "useful" you care for).
I don't think MULE consumes any resources in Unibyte mode.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Silence!" cries Freydag. "I did not call thee in for a consultation!"
"They are my innards! I will not have them misread by a poseur!"
next prev parent reply other threads:[~1998-08-17 12:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-12 22:41 Lars Magne Ingebrigtsen
1998-08-13 15:17 ` Edward J. Sabol
1998-08-13 16:33 ` Lars Magne Ingebrigtsen
1998-08-14 11:22 ` Jan Vroonhof
1998-08-14 17:45 ` Lars Magne Ingebrigtsen
[not found] ` <x7r9ykaea2.fsf@peorth.gweep.net>
1998-08-13 19:41 ` Lars Magne Ingebrigtsen
1998-08-13 20:25 ` Jake Colman
1998-08-13 20:42 ` William M. Perry
1998-08-14 7:27 ` Steinar Bang
1998-08-22 12:01 ` Dave Love
1998-08-13 19:44 ` François Pinard
[not found] ` <x7hfzgv8is.fsf@peorth.gweep.net>
1998-08-13 23:06 ` François Pinard
1998-08-14 7:28 ` Steinar Bang
[not found] ` <x7soize2td.fsf@peorth.gweep.net>
1998-08-17 12:53 ` Hrvoje Niksic [this message]
1998-08-17 13:47 ` Robert Bihlmeyer
1998-08-14 10:58 ` Kai Grossjohann
1998-08-14 13:00 ` luis fernandes
1998-08-14 18:15 ` SL Baur
[not found] ` <x7pve3e2md.fsf@peorth.gweep.net>
1998-08-22 12:24 ` Dave Love
[not found] ` <x7d89rrg0f.fsf@peorth.gweep.net>
1998-08-24 22:31 ` Dave Love
1998-08-24 22:58 ` Dave Love
1998-08-25 6:13 ` Lars Magne Ingebrigtsen
[not found] ` <x7r9y5di7z.fsf@peorth.gweep.net>
1998-08-26 18:12 ` Dave Love
[not found] ` <x7zpcq2ws8.fsf@peorth.gweep.net>
1998-08-27 20:51 ` Dave Love
1998-08-25 1:15 ` SL Baur
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=kigemufydjx.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).