unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: PGTK+ warning
Date: Tue, 15 Nov 2022 16:16:57 +0100	[thread overview]
Message-ID: <87iljg6y5o.fsf@gmail.com> (raw)
In-Reply-To: <jwv8rkcfgc1.fsf-monnier+emacs@gnu.org>


Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> writes:

> Since you should likely (re)start Emacs every month or so, it shouldn't
> be a problem.  If you constantly start new Emacs sessions, then maybe
> that's the problem you should solve first.

Actually, I do start Emacs every time, mostly because:

1) I'm still experimenting with my init file, and I want changes to be
effective. I *could* just re-evaluate my init file, but I'd then have to
deal with side-effects (like removing functions from hooks), and
restarting Emacs is just way faster.

M-x restart-emacs would be great for this precise purpose, but somehow
it close Emacs, but doesn't restart it. Maybe is it an issue of Xorg?
I'll try that as well.

2) I power off my PC every evening :-)

IIUC, are there resons for which I should keep both PC and Emacs
running?

-- 
Alessandro Bertulli



  parent reply	other threads:[~2022-11-15 15:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 10:00 PGTK+ warning Alessandro Bertulli
2022-11-15 10:37 ` Po Lu
2022-11-15 15:14   ` Alessandro Bertulli
2022-11-15 14:22 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-15 15:14   ` Emanuel Berg
2022-11-15 15:16   ` Alessandro Bertulli [this message]
2022-11-15 15:35     ` Emanuel Berg
2022-11-15 18:05       ` Alessandro Bertulli
2022-11-15 18:22         ` Emanuel Berg
2022-11-16 22:41           ` Alessandro Bertulli
2022-11-16 23:30             ` Emanuel Berg
2022-11-19 10:21               ` Alessandro Bertulli
2022-11-15 16:03     ` Stefan Monnier
2022-11-15 18:02       ` Alessandro Bertulli
2022-11-15 18:17         ` Eli Zaretskii
2022-11-16 22:42           ` Alessandro Bertulli
2022-11-16 23:19             ` Emanuel Berg
2022-11-19 10:25               ` Alessandro Bertulli
2022-11-22 15:34                 ` Emanuel Berg
2022-11-30 22:39                   ` Alessandro Bertulli
2022-12-01  0:21                     ` Emanuel Berg
2022-12-01  0:23                       ` Emanuel Berg
2022-12-03  0:58                         ` David Masterson
2022-11-17  6:25             ` 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

  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=87iljg6y5o.fsf@gmail.com \
    --to=alessandro.bertulli96@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
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).