unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Károly Lorentey" <karoly@lorentey.hu>
Cc: emacs-devel@gnu.org
Subject: Re: minibuffer-exit when emacsclient executes Lisp code
Date: Thu, 17 May 2007 09:48:42 -0400	[thread overview]
Message-ID: <jwvbqgjlg58.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f2ev68$73c$1@sea.gmane.org> ("Károly Lo"'s message of "Wed\, 16 May 2007 14\:58\:40 +0200")

> the first real terminal only on the second run.  One way to reduce
> flickering would be to delay terminal initialization until after .emacs
> is loaded.  Is this what you mean?

I've been using a local hack which does just that.  Funnily enough it
doesn't remove all frame-resizing.  Maybe it's a bug in my hack, of course.

> Wouldn't that make it harder to debug .emacs errors?

Not really, no.  But it did break part of my .emacs which called
`frame-parameter' or something like that.

In any case, w.r.t calling `toplevel' I agree that we should probably not do
that when processing a "-eval" (after all, the user can explicitly add
a call to (toplevel) in the Elisp code passed to the Emacs session).
The only reason why it does do it currently, is because it seemed too much
trouble to try and distinguish this case.  Maybe the recursion-depth check
should be moved elsewhere where it's easier to determine whether -eval was
used or not.


        Stefan

  parent reply	other threads:[~2007-05-17 13:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 10:10 minibuffer-exit when emacsclient executes Lisp code Klaus Zeitler
2007-05-15 20:47 ` Lennart Borgman (gmail)
2007-05-16  8:28   ` Klaus Zeitler
2007-05-16 11:28     ` Lennart Borgman (gmail)
2007-05-16 11:43       ` David Kastrup
2007-05-16 11:49         ` Lennart Borgman (gmail)
2007-05-16 12:58         ` Károly Lo"rentey
2007-05-16 13:04           ` Juanma Barranquero
2007-05-16 13:51           ` David Kastrup
2007-05-16 14:15           ` Klaus Zeitler
2007-05-17 13:48           ` Stefan Monnier [this message]
2007-05-16 14:10       ` Klaus Zeitler
2007-05-16 14:47         ` Lennart Borgman (gmail)
2007-05-23  9:59       ` Klaus Zeitler
2007-05-23 10:12         ` Lennart Borgman (gmail)
2007-05-23 15:03           ` Stefan Monnier
2007-05-23 18:56           ` Richard Stallman
2007-05-23 19:42             ` Lennart Borgman (gmail)
2007-05-24 13:13             ` Stefan Monnier
2007-05-25  7:37               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2007-05-16 14:01 karoly
2007-05-16 14:18 ` Juanma Barranquero
2007-05-16 14:35   ` Károly Lőrentey
2007-05-16 14:55     ` Juanma Barranquero
2007-05-17 13:28       ` Dan Nicolaescu
2007-05-16 14:41 ` David Kastrup
2007-05-16 14:58   ` Juanma Barranquero
2007-05-16 15:52   ` Károly Lo"rentey
2007-05-16 23:36   ` Kenichi Handa

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=jwvbqgjlg58.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=karoly@lorentey.hu \
    /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).