From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Nikolaj Schumacher <me@nschum.de>
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 18:10:17 +0200 [thread overview]
Message-ID: <48EF7E69.1090109@gmail.com> (raw)
In-Reply-To: <m2abdccuq4.fsf@nschum.de>
Nikolaj Schumacher wrote:
> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> wrote:
>
>> Yes, in winsize.el that comes with nXhtml.
>
> If you don't mind me asking, but why does it?
>
> It sounds very interesting and useful beyond nxhtml. Why isn't it
> packaged on it's own?
Because I do not have time to do it in another way. I constantly fix
small bugs that I find and then it just takes to much time uploading a
file to different places.
I do not think it is a problem any more since you can easily get a
single file from the nXhtml repository at Launchpad.
> (I'm a bit bothered by big modes that do everything. ECB forces its own
> window configuration. The Ruby on Rails mode has its own snippet
> mechanism. I feel that such bundling limits the overall usefulness.)
I really feel the opposite! Not bundling things can make things take
forever to setup.
In the particular case of winsize.el this is not the case of course, but
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.
Bundling lowers the number of possible combinations without any serious
restrictions. Any user who prefer shooting themselves in the foot are
free to do so, but those who do not have time with it can use the bundle ;-)
More seriously another mechanism for bundling would be better. A very
good sysstem for version control and dependencies is what I would prefer
- if someone has time to write it, test it, etc. And of course get
people to use it, mark all old dependencies ...
> regards,
> Nikolaj Schumacher
>
next prev parent reply other threads:[~2008-10-10 16:10 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) [this message]
2008-10-10 19:04 ` Nikolaj Schumacher
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=48EF7E69.1090109@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=me@nschum.de \
--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).