From: Nikolaj Schumacher <me@nschum.de>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>, help-gnu-emacs@gnu.org
Subject: Re: split screen horizontally into three equally spaced sections
Date: Fri, 10 Oct 2008 21:04:37 +0200 [thread overview]
Message-ID: <m21vyoclve.fsf@nschum.de> (raw)
In-Reply-To: <48EF7E69.1090109@gmail.com> (Lennart Borgman's message of "Fri\, 10 Oct 2008 18\:10\:17 +0200")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> wrote:
> when it comes to more complex things then I definitively prefer
> bundling. Remember that complexity tends to grow exponentially with the
> number of involved things.
Exactly. If two things are tied-together, there are more things
involved. If they are separate, complexity is actually reduced.
We're talking about slightly different things, I think. When there are
real dependencies, I don't mind packaging. It's a sane choice in
absence of package management. But many packages have artificial
dependencies that wouldn't have to exist.
I don't know about your package, so I don't want to make any
assumptions. But, for example, ECB can only reasonably used with the
included (brain-dead) window management. There is no way to just use
the (excellent) class browser. That's a serious restriction...
It seems that winsize is optional, as well as separately usable. I don't
mind that they're in the same zip file. I just think that bundling
generally increases the risk that they needlessly get tangled together.
I hope that doesn't happen.
regards,
Nikolaj Schumacher
next prev parent reply other threads:[~2008-10-10 19:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 11:52 split screen horizontally into three equally spaced sections Gil
2008-09-14 12:09 ` harven
2008-09-14 12:48 ` Rupert Swarbrick
2008-09-14 16:01 ` Peter Dyballa
2008-09-16 5:22 ` Allan Gottlieb
[not found] ` <mailman.19329.1221542577.18990.help-gnu-emacs@gnu.org>
2008-10-07 22:26 ` maps.automation58
2008-10-08 19:15 ` Allan Gottlieb
2008-10-08 22:01 ` Bastien
[not found] ` <mailman.622.1223503318.25473.help-gnu-emacs@gnu.org>
2008-10-10 7:11 ` Sébastien Vauban
2008-10-10 8:00 ` harven
2008-10-10 8:02 ` Lennart Borgman (gmail)
2008-10-10 15:53 ` Nikolaj Schumacher
2008-10-10 16:10 ` Lennart Borgman (gmail)
2008-10-10 19:04 ` Nikolaj Schumacher [this message]
2008-10-10 19:36 ` Lennart Borgman
2008-10-11 12:57 ` Nikolaj Schumacher
[not found] ` <mailman.852.1223729847.25473.help-gnu-emacs@gnu.org>
2008-10-11 14:07 ` Andreas Politz
2008-10-10 8:38 ` Bastien
[not found] ` <mailman.767.1223627907.25473.help-gnu-emacs@gnu.org>
2008-10-10 10:23 ` Sébastien Vauban
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=m21vyoclve.fsf@nschum.de \
--to=me@nschum.de \
--cc=help-gnu-emacs@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=zthjwsqqafhv@spammotel.com \
/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).