unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: lekktu@gmail.com, yandros@MIT.EDU, monnier@iro.umontreal.ca,
	emacs-devel@gnu.org
Subject: Re: Annoying (frameset bug?): desktop-mode and maxmized frame
Date: Tue, 12 Nov 2013 18:10:01 +0200	[thread overview]
Message-ID: <83zjp91u06.fsf@gnu.org> (raw)
In-Reply-To: <874n7ikx48.fsf@gmail.com>

> From: Jambunathan K <kjambunathan@gmail.com>
> Date: Tue, 12 Nov 2013 10:57:51 +0530
> Cc: Juanma Barranquero <lekktu@gmail.com>,
> 	Stefan Monnier <monnier@iro.umontreal.ca>,
> 	Emacs developers <emacs-devel@gnu.org>
> 
> chad <yandros@MIT.EDU> writes:
> 
> > "The users might be unable to stop themselves from manually resizing
> > frames in the middle of startup, even though they know they
> > shouldn't."
> 
> If a user does this his Emacs is USELESS (as my screenshot shows).
> There are countless times that I had to restart my Emacs just to
> workaround the issue.

That sounds strange: at the very least, you should be able to invoke
functions and commands from the *scratch* buffer, and the first
command could be to set the frame dimensions to something usable.
Alternatively, you could create a new frame (which supposedly will use
default-frame-alist, and thus be of reasonable dimensions), and then
kill the initial frame.  Both alternatives sound better than
restarting Emacs.

Am I missing something?



  reply	other threads:[~2013-11-12 16:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  5:05 Annoying (frameset bug?): desktop-mode and maxmized frame Jambunathan K
2013-11-10 12:25 ` Juanma Barranquero
2013-11-10 13:39   ` Jambunathan K
2013-11-10 17:29     ` Juanma Barranquero
2013-11-10 17:40       ` Jambunathan K
2013-11-10 17:47         ` Juanma Barranquero
2013-11-11  7:52           ` Jambunathan K
2013-11-11  8:26             ` Jambunathan K
2013-11-11 13:29               ` Stefan Monnier
2013-11-11 10:30             ` Juanma Barranquero
2013-11-11 10:34               ` Jambunathan K
2013-11-11 12:29                 ` Juanma Barranquero
2013-11-11 14:04                   ` Stefan Monnier
2013-11-11 14:15                     ` Juanma Barranquero
2013-11-11 18:16                       ` chad
2013-11-12  5:27                         ` Jambunathan K
2013-11-12 16:10                           ` Eli Zaretskii [this message]
2013-11-12 16:24                             ` Jambunathan K
2013-11-12 16:56                               ` Eli Zaretskii
2013-11-11 15:45                   ` Jambunathan K
2013-11-11 15:55                     ` Juanma Barranquero
2013-11-11 16:46                     ` Eli Zaretskii
2013-11-12  8:43                       ` Jambunathan K
2013-11-12 16:15                         ` Eli Zaretskii
2013-11-12 16:38                           ` Jambunathan K
2013-11-11  2:50         ` Stephen J. Turnbull
2013-11-11  4:47           ` Jambunathan K
2013-11-11  5:04             ` Stephen J. Turnbull
2013-11-11  5:12               ` Jambunathan K
2013-11-11  8:39               ` Jambunathan K
2013-11-11 10:27             ` Juanma Barranquero
2013-11-11 11:07               ` Jambunathan K
2013-11-11 12:32                 ` Juanma Barranquero
2013-11-11 15:55                   ` Jambunathan K
2013-11-11 15:58                     ` Juanma Barranquero
2013-11-11 10:23           ` Juanma Barranquero
2013-11-11 10:31             ` Jambunathan K
2013-11-11 10:31               ` Juanma Barranquero
2013-11-11 10:40                 ` Jambunathan K
2013-11-11 12:30                   ` Juanma Barranquero
2013-11-11 11:23         ` Jarek Czekalski
2013-11-11 11:33           ` Jambunathan K

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=83zjp91u06.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=lekktu@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=yandros@MIT.EDU \
    /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).