all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: About desktop file
Date: Tue, 13 Sep 2016 23:35:31 +0200	[thread overview]
Message-ID: <6a4c73a9-0581-137f-6b1b-20136006e7f4@alice.it> (raw)
In-Reply-To: <83r38n9902.fsf@gnu.org>



Il 13/09/2016 16:20, Eli Zaretskii ha scritto:
>> Cc: emacs-devel@gnu.org
>> From: Angelo Graziosi <angelo.graziosi@alice.it>
>> Date: Mon, 12 Sep 2016 22:14:21 +0200
>>
>> Il 12/09/2016 18:43, Eli Zaretskii ha scritto:
>>>
>>> Does Martin's advice give you what you want?  I think different users
>>> will have different expectations regarding what frame parameters of
>>> existing frames should be restored, so customization is the right way
>>> of fitting this to your needs.
>>>
>>
>> I don't understand why an user, that tries to customize the font, has
>> the expectation to find this in the second frame and not in the first.
>
> Because frames loaded from the desktop file override the init file
> settings.

..but the font configuration is not matter that desktop file should handle..

desktop file could override what isn't yet in the init file but not what 
it has.. otherwise which is the role of init file?

In any case, it seems we are wasting our time. If you think this 
behavior is OK, leave as it is. As I wrote, I will continue to 
regenerate the desktop file when I will find these kind of "issues" 
because for me this is the best and clean solution.

Thanks,
  Angelo.


PS. Just for the record, this init file is sufficient to have the new 
font in the first frame restored by desktop file:

$ cat init.el
(add-to-list 'initial-frame-alist '(font . "Source Code Pro 13"))
(add-to-list 'default-frame-alist '(font . "Source Code Pro 13"))

(setq desktop-base-file-name "~/.emacs.d/desktop")

(setq desktop-base-lock-name "~/.emacs.d/desktop.lock")

(desktop-save-mode 1)





  reply	other threads:[~2016-09-13 21:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11  8:31 About desktop file Angelo Graziosi
2016-09-11 16:34 ` Eli Zaretskii
2016-09-11 20:13   ` Angelo Graziosi
2016-09-11 21:32     ` Chad Brown
2016-09-11 23:43       ` Angelo Graziosi
2016-09-12 16:47         ` Eli Zaretskii
2016-09-12 16:43     ` Eli Zaretskii
2016-09-12 20:14       ` Angelo Graziosi
2016-09-13 14:20         ` Eli Zaretskii
2016-09-13 21:35           ` Angelo Graziosi [this message]
2016-09-14 17:30             ` Eli Zaretskii
2016-09-15 13:25               ` Angelo Graziosi
2016-09-15 14:41                 ` Eli Zaretskii
2016-09-15 18:01                   ` Angelo Graziosi
2016-09-17  9:21                     ` Eli Zaretskii
2016-09-17 13:04                       ` Angelo Graziosi
2016-09-17 13:36                         ` Eli Zaretskii
2016-09-12  6:23 ` martin rudalics
2016-09-12 20:07   ` Angelo Graziosi
2016-09-13 14:22     ` Eli Zaretskii

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=6a4c73a9-0581-137f-6b1b-20136006e7f4@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.