From: "B. T. Raven" <nihil@nihilo.net>
To: help-gnu-emacs@gnu.org
Subject: Re: How to configure default widow splitting orientation
Date: Fri, 16 Jan 2009 17:03:02 -0600 [thread overview]
Message-ID: <NeCdnWjzuLO5j-zUnZ2dnUVZ_rXinZ2d@sysmatrix.net> (raw)
In-Reply-To: <mailman.5091.1232146174.26697.help-gnu-emacs@gnu.org>
David Abrahams wrote:
> on Fri Jan 16 2009, David Abrahams <dave-AT-boostpro.com> wrote:
>
>> on Thu Sep 04 2008, "Francis Moreau" <francis.moro-AT-gmail.com> wrote:
>>
>>> On Wed, Sep 3, 2008 at 6:18 PM, weber <hugows@gmail.com> wrote:
>>>> I used this for a while:
>>>>
>>>>
>> http://tsdh.wordpress.com/2007/03/09/automatically-split-window-horizontally-if-current-window-is-wide-enough/
>>> Thanks !
>>>
>>> This should do the trick until I upgrade to emacs 23.1
>> Hmm, I've been using something else (even though I am on an emacs
>> snapshot and I should have a customizable
>> `split-window-preferred-function'). I'm not sure yet whether my
>> approach has any advantages over the customization; if not, I'm
>> inclined to drop it.
>>
>> See
>> http://github.com/techarcana/elisp/blob/7eb6347a0aab8f444c7b645f4b5383613493a913/elisp/config.d/window-splitting.el
>
> Okay, this is really weird. First I tried disabling my advice and
> customizing split-window-preferred-function to 'split-window-horizontally
> instead. All heck broke loose: just trying to do tab completion in the
> minibuffer would result in "Attempt to split minibuffer window" errors.
> Then I removed the customization and left my advice disabled.
>
> Everything worked exactly as it had seemed to with the advice
> enabled. Beautiful!
>
> Why is that weird, though? Well, I finally broke down and wrote that
> advice because I had gotten tired of getting the wrong window splits
> while using my current version of Emacs, *a CVS snapshot from earlier
> this month*.
>
> Hmm, (emacs-version) says:
>
> "GNU Emacs 23.0.60.2 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2009-01-05 on mcbain"
>
> where is 23.1 and why does my snapshot have an earlier version number?
I don't think it exists yet. That's why Hugo wrote "until I can ...."
The 23.0.... whatever, suffixes are something like a beta version.
>
> Thanks,
>
next prev parent reply other threads:[~2009-01-16 23:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.18205.1220366692.18990.help-gnu-emacs@gnu.org>
2008-09-02 17:12 ` How to configure default widow splitting orientation Pascal J. Bourguignon
2008-09-02 19:49 ` Tassilo Horn
2008-09-03 10:09 ` Francis Moreau
2008-09-03 12:06 ` Lave
2008-09-03 12:28 ` Francis Moreau
[not found] ` <mailman.18309.1220444927.18990.help-gnu-emacs@gnu.org>
2008-09-03 16:18 ` weber
2008-09-04 7:23 ` Francis Moreau
2009-01-16 22:12 ` David Abrahams
2009-01-16 22:49 ` David Abrahams
[not found] ` <mailman.5091.1232146174.26697.help-gnu-emacs@gnu.org>
2009-01-16 23:03 ` B. T. Raven [this message]
2008-09-02 17:57 ` David Hansen
2008-09-03 10:10 ` Francis Moreau
2008-09-02 14:44 Francis Moreau
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=NeCdnWjzuLO5j-zUnZ2dnUVZ_rXinZ2d@sysmatrix.net \
--to=nihil@nihilo.net \
--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).