all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: 'fullscreen 'fullheight
Date: Tue, 02 May 2006 10:25:59 -0600	[thread overview]
Message-ID: <e38182$hqp$1@sea.gmane.org> (raw)
In-Reply-To: <albquhl8v3.fsf@quant8.janestcapital.quant>

Sam Steingold wrote:
> GNU Emacs 22.0.50.24 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
>  of 2006-05-01 on quant8
> 
> I use Emacs on various machines with different X screen parameters,
> and I like Emacs frames to have maximum possible height.
> I used to use this:
> 
> (defun sds-frame-normaize (&optional frame move)
>   "the frame --> top right; almost full size"
>   (interactive)
>   (unless frame (setq frame (selected-frame)))
>   (set-frame-parameter frame 'fullscreen nil)
>   (set-frame-parameter frame 'fullscreen 'fullheight)
>   (set-frame-parameter frame 'fullscreen nil)
>   (when move
>     (set-frame-position frame 0 0))
>   (let ((height (- (frame-height) (eval-when-compile (if sds-winnt 1 4)))))
>     (set-frame-height frame height)
>     (set-frame-width frame 80)
>     (set-frame-parameter frame 'top '(+ -5))
>     height))
>     
> (I welcome suggestion on how to accomplish the same easier!)
> 
> recently I noticed the following unpleasant behavior:
> 
> $ emacs -q
> (frame-height) C-j
> ==> 43
> (set-frame-parameter nil 'fullscreen 'fullheight) C-j
> ==> nil
> (frame-height) C-j
> ==> 43
> 
> now the X window has the correct size, but the emacs frame does not!
> ((frame-height) returns the old value)
> also, set-frame-parameter takes several seconds to execute!

What is your intent in specifying fullscreen as nil, then fullheight,
then nil, and then specifying height explicitly anyway?

What should Emacs do when the frame parameters include both fullscreen
and height or width, which may conflict?

-- 
Kevin Rodgers

  reply	other threads:[~2006-05-02 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 21:42 'fullscreen 'fullheight Sam Steingold
2006-05-02 16:25 ` Kevin Rodgers [this message]
2006-05-03  8:02 ` Kim F. Storm

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='e38182$hqp$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.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 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.