all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: Michael Cadilhac <michael.cadilhac@lrde.org>, emacs-devel@gnu.org
Subject: Re: Strange things with (shrink-window).
Date: Thu, 17 Nov 2005 09:13:25 +1300	[thread overview]
Message-ID: <17275.37605.434203.636150@kahikatea.snap.net.nz> (raw)
In-Reply-To: <E1EcKpY-0007Ln-Tr@fencepost.gnu.org>

Richard M. Stallman writes:
 >       $ emacs -Q (with or without -nw)
 > 
 >       Then C-x 3 C-x 2, then go to the window on the right.
 > 
 >       Now, M-x global-set-key RET F10 RET shrink-window RET
 > 
 >       Then press F10: nothings happen.
 > 
 >       Press F10 and stay on the touch. The window on the upper left will
 >       start to slowly and randomly shrink.
 > 
 > I agree that is a bug.  If the first invocation of F10 does nothing,
 > all further invocations should do nothing.  (It is supposed to
 > vertically shrink the window, and that can't be done, since it has no
 > vertical peers.)
 > 
 > Can someone please debug this and reply to this message?  I am
 > overloaded and cannot do it myself.  But fixing bugs like this is
 > important for the release--there's no point starting a pretest to find
 > out additional bugs, if we aren't fixing the ones we know about.

There is a point: to progress the release.  This is a really obscure bug.
Whenever, or if ever, Emacs is released, it will have bugs.  Its a question of
balancing the inconvenience of those bugs against the benefit of the
availability to, and feedback from, a large number of users.  I realise that
philosophers talk about freedom whereas only supermarkets get excited about
availability, but its a shame.

Nick

      reply	other threads:[~2005-11-16 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87hdady70s.fsf@mahaena.lrde>
2005-11-16 10:47 ` Strange things with (shrink-window) Richard M. Stallman
2005-11-16 20:13   ` Nick Roberts [this message]

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=17275.37605.434203.636150@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=michael.cadilhac@lrde.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.