unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ben Key <bkey76@gmail.com>
Cc: bobfloyd@comcast.net, lekktu@gmail.com, 8212@debbugs.gnu.org
Subject: bug#8212: Emacs 23.3.rc2: Frame height setting lost when entire frame dragged around on screen
Date: Fri, 11 Mar 2011 20:25:34 +0200	[thread overview]
Message-ID: <83d3lxtsyp.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimDgfkbko0DQ+p20jgtivRxVmwhPxuwzA8z9Mbd@mail.gmail.com>

> From: Ben Key <bkey76@gmail.com>
> Date: Fri, 11 Mar 2011 10:52:39 -0600
> Cc: Juanma Barranquero <lekktu@gmail.com>, bobfloyd@comcast.net, 8212-done@debbugs.gnu.org
> 
> Should we document this feature on the "EmacsWiki: Category WThirty Two"
> page?

I don't care about the wiki.  I think the wiki is a bastardly place to
put user-level documentation about a software package: bare,
unstructured, unmaintained, and without any decent QA.  Basically, a
dump.

For me, anything that's worth being documented should be in Emacs, in
one of the documents that come with it.  (One such document we didn't
yet consider is the Emacs FAQ (doc/misc/faq.texi).  Maybe I can
persuade you guys to document this there.)

If it doesn't deserve to be in the FAQ or elsewhere in Emacs, then to
me it means that it doesn't deserve to be mentioned anywhere.

> While I believe it should not be mentioned in etc/PROBLEMS since it
> is an operating system feature and not a bug, it should be documented
> somewhere.  That way anyone who encounters this feature in the future will
> see it documented so they know that Emacs is supposed to behave that way.

If that is all you want, there's no need to do anything at all:
googling for this issue will surely find it years from now.





  parent reply	other threads:[~2011-03-11 18:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 20:43 bug#8212: Emacs 23.3.rc2: Frame height setting lost when entire frame dragged around on screen Bob Floyd
2011-03-10  5:24 ` Ben Key
2011-03-10 14:45   ` Juanma Barranquero
2011-03-10 17:32     ` Eli Zaretskii
2011-03-10 19:22       ` Juanma Barranquero
2011-03-10 19:33         ` Eli Zaretskii
2011-03-10 19:35           ` Juanma Barranquero
2011-03-11  0:18             ` Ben Key
2011-03-11  0:21               ` Juanma Barranquero
2011-03-11 10:31                 ` Eli Zaretskii
     [not found]                   ` <AANLkTimDgfkbko0DQ+p20jgtivRxVmwhPxuwzA8z9Mbd@mail.gmail.com>
2011-03-11 18:25                     ` Eli Zaretskii [this message]
2011-03-11 19:30                       ` Juanma Barranquero
2011-03-10  5:56 ` Eli Zaretskii
2011-03-10 16:02 ` Ben Key
2011-03-10 17:08 ` Bob Floyd

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=83d3lxtsyp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=8212@debbugs.gnu.org \
    --cc=bkey76@gmail.com \
    --cc=bobfloyd@comcast.net \
    --cc=lekktu@gmail.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.
Code repositories for project(s) associated with this public inbox

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

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).