unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [werner@suse.de: Several problems in KDE/KWin]
Date: Fri, 07 Dec 2007 20:08:00 +0100	[thread overview]
Message-ID: <jeir3auxv3.fsf@sykes.suse.de> (raw)
In-Reply-To: <87k5nqqtfv.fsf@member.fsf.org> (Tassilo Horn's message of "Fri\,  07 Dec 2007 18\:57\:08 +0100")

Tassilo Horn <tassilo@member.fsf.org> writes:

> Richard Stallman <rms@gnu.org> writes:
>
>>   Emacs does not un-maximize in KDE/KWin
>
> [...]
>
>> After maximizing an emacs window, it is not possible to un-maximise it.
>> It may depend on font size and desktop geometry.  I have these in
>> Xresources:
>>  Emacs.font:     10x20
>>  Emacs.geometry: 80x38
>>  Size of desktop is 1400x1050.
>> The symptom is that after maximizing, the "maximize/un-maximize" button stays
>> in the "maximize" state (one square), intead of going to the "un-maximize"
>> state (two squares).
>
> I think the problem is that Emacs cannot be resized stepless, but only
> in steps of columns and lines depending on the size of the used font.

I don't think so.  Other programs like xterm also resize in steps, but
still can be properly maximized/unmaximized.

> So if Emacs is maximized in KDE it's most probably not as big as the
> usable space of the desktop is.  I'm not sure, but I think because of
> that kwin thinks it's not maximized.

If you try to maximize a second time the frame is actually truely
maximized.  But unmaximizing restores intermediate, nearly maximized
size, not the original one.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-12-07 19:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 17:18 [werner@suse.de: Several problems in KDE/KWin] Richard Stallman
2007-12-07 17:57 ` Tassilo Horn
2007-12-07 19:08   ` Andreas Schwab [this message]
2007-12-08  0:07     ` Stephen Berman
2007-12-08  9:30       ` Jan Djärv
2007-12-08 12:30         ` Stephen Berman
2008-03-01 15:05           ` Jan Djärv
2008-03-01 16:13             ` Andreas Schwab
2008-03-01 16:18               ` Jan Djärv
2008-03-01 17:13                 ` Andreas Schwab
2008-03-02  5:58                   ` Jan Djärv
2008-03-02 10:36                     ` Andreas Schwab
2008-03-02 12:26                       ` Jan Djärv
2008-03-03 14:15             ` Stephen Berman
2007-12-08  9:41       ` Andreas Schwab
2007-12-08 12:31         ` Stephen Berman
2007-12-08 15:40           ` Andreas Schwab
2007-12-08 15:51             ` Stephen Berman
2007-12-08 17:32               ` Andreas Schwab
2007-12-08 17:43                 ` Stephen Berman

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=jeir3auxv3.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.
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).