unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Norman Ramsey <nr@cs.tufts.edu>
Cc: 33686@debbugs.gnu.org
Subject: bug#33686: 25.1; desktop-mode restore, issue with frame size
Date: Sun, 09 Dec 2018 18:28:56 +0200	[thread overview]
Message-ID: <83va423bqv.fsf@gnu.org> (raw)
In-Reply-To: <b911s6qd73r.fsf@cs.tufts.edu> (message from Norman Ramsey on Sun, 09 Dec 2018 10:59:04 -0500)

> From: Norman Ramsey <nr@cs.tufts.edu>
> Date: Sun, 09 Dec 2018 10:59:04 -0500
> 
> 
> I'm using (desktop-save-mode 1) to save a session which I then reload,
> but logging in remotely from a different machine with a different
> resolution display. Something stored in the desktop winds up setting
> frame width to 150 characters rather than the 87 characters it was saved
> with.  Height seems unaffected.
> 
> In detail:
> 
>   - Start emacs on machine `homedog` with one monitor, resolution
>     3840x2160. 
>   - Exit emacs, writing .desktop file.
>   - Remote login to `homedog` from machine `jar`, using `ssh -X` to
>     forward the X server connection.  Machine `jar` has one monitor,
>     resolution 1920x1200.  
>   - Start emacs on homedog, but with DISPLAY environment variable set to
>     `localhost:10.0`, which is the forwarded X connection.
> 
> When the dust settles after initialization, the emacs frame seems to be
> about the right height, but it is much wider than it should be.

Do you also have any init files?  If so, please empty them and try
again.  It's important to understand whether the problem is with
desktop-save-mode alone, or some of your other customizations
interfere.





  reply	other threads:[~2018-12-09 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09 15:59 bug#33686: 25.1; desktop-mode restore, issue with frame size Norman Ramsey
2018-12-09 16:28 ` Eli Zaretskii [this message]
2018-12-09 22:37   ` Robert Pluim
2018-12-22 21:34   ` Norman Ramsey
2019-06-21 13:53 ` bug#33686: close this bug Norman Ramsey
2019-06-21 14:16   ` Noam Postavsky

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=83va423bqv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33686@debbugs.gnu.org \
    --cc=nr@cs.tufts.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).