unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: jidanni@jidanni.org
Cc: rfrancoise@debian.org, 3643@debbugs.gnu.org
Subject: bug#3643: emacs -Q doesn't fit on the user's screen
Date: Wed, 20 Jan 2010 08:18:08 +0100	[thread overview]
Message-ID: <4B56AE30.4090109@swipnet.se> (raw)
In-Reply-To: <87ska1e0f3.fsf@jidanni.org>

jidanni@jidanni.org skrev:
> JD> Again, details are missing.
> Can you provide me with a script that I can run that will gather the
> exact information you need beyond the screenshots and details I gave
> earlier in this bug. For instance, as a total font dummy that I am, I
> need a script that can tell you what fonts it is using, because I don't
> really know... better yet, perhaps the Debian people can enhance their
> report-emacs-bug function so it will provide the missing information
> beyond what it gives currently:

Just put the cursor on one character in Emacs *scratch* buffer and do
C-u C-x =

That gives you the font.

% xwininfo -all
and click in Emacs gives window sizes.

% xwininfo -frame
and click the window manager title bar for Emacs gives size of the title bar.

That last part may be it though.  As the title bar size isn't known at frame 
create time, we can't adjust for it.  I'll have to think about that.

A better strategy might be if 40 lines doesn't seem to fit, just try 20.
If that doesn't seem to fit, try 10.

	Jan D.








  reply	other threads:[~2010-01-20  7:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87636liaoo.fsf@tochka.ru>
2009-06-21 20:50 ` bug#3643: minibuffer beyond end of screen in emacs23 jidanni
2010-01-15 12:14   ` bug#3643: emacs -Q doesn't fit on the user's screen jidanni
2010-01-15 15:31     ` Jan Djärv
2010-01-15 17:08     ` Jan Djärv
2010-01-16  1:10   ` jidanni
2010-01-20  3:57   ` jidanni
2010-01-20  6:26     ` Jan Djärv
2010-01-20  6:49   ` jidanni
2010-01-20  7:18     ` Jan Djärv [this message]
2010-01-20  6:53   ` jidanni
2010-01-20  7:31   ` jidanni
2010-01-20  8:27     ` Jan Djärv
2010-01-20  9:27       ` martin rudalics
2010-01-20  9:58         ` Jan Djärv
2010-01-20 10:59           ` martin rudalics
2010-01-20 11:14             ` Jan Djärv
2010-01-21 14:12             ` Stefan Monnier
2010-01-25  7:52       ` Jan Djärv
2010-01-21 23:53   ` jidanni
2010-01-25 23:05   ` jidanni
2010-01-26  6:56     ` Jan Djärv
2010-01-27  5:17   ` jidanni
2010-01-27  6:21     ` Jan Djärv
2010-01-28  2:23       ` Chong Yidong
2010-01-28  7:18         ` Jan Djärv
2010-01-28 19:06           ` Stefan Monnier
2010-01-29 16:36             ` Chong Yidong
2010-01-29 18:52               ` Stefan Monnier
2010-01-27  6:52   ` jidanni
2010-01-27  9:00     ` Jan Djärv
2010-01-27 10:15   ` jidanni
2010-01-29 10:50   ` bug#3643: Bug#567083: " jidanni
2010-01-29 11:23   ` jidanni
2010-01-29 12:14     ` Evgeny M. Zubok
2010-01-29 12:33   ` jidanni
2010-02-21  9:45   ` jidanni
2010-01-12 23:07 bug#3643: " jidanni
2010-01-13  7:37 ` Yavor Doganov
2010-01-13  7:42 ` Jan D.
2010-01-13  8:49   ` Romain Francoise
2010-01-13 21:14     ` jidanni
2010-01-13 11:24   ` Jan D.
2010-01-14  3:48     ` jidanni

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=4B56AE30.4090109@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=3643@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=rfrancoise@debian.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 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).