unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Chong Yidong <cyd@stupidchicken.com>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Splash screen and gnuserv
Date: Wed, 13 Sep 2006 09:25:33 +0200	[thread overview]
Message-ID: <4507B26D.7060800@student.lu.se> (raw)
In-Reply-To: <u1wqgutj4.fsf@jasonrumney.net>

Jason Rumney wrote:
> Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>
>   
>> Thanks. Does that mean that there is something in emacsserver that
>> turns off the splash screen?
>>     
>
> Was that what the problem was? It was not clear from the mail you
> forwarded, but I thought the problem being reported was that
> viper-mode came up in insert mode.
>   

Nearly, but not quite. If the splash screen is active when gnuserv 
recieves the command to open a new file then something strange happens. 
The new file is shown, but the mode line shows the brackets (like 
[(Emacs-Lisp hs)] for recursive editing. There is a 'V' on the modeline 
so Viper should be in vi mode.

However when any key is typed it is inserted in the buffer instead of 
executed by viper. When the splash screen finishes the brackets 
disappears and now everything works as expected. A workaround for this 
problem is to turn off the splash screen.

So maybe this should be tested again with emacsserver? Sorry for not 
beeing clear enough before.

  reply	other threads:[~2006-09-13  7:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 22:36 Splash screen and gnuserv Lennart Borgman
2006-09-13  3:12 ` Chong Yidong
2006-09-13  6:26   ` Lennart Borgman
2006-09-13  7:15     ` Jason Rumney
2006-09-13  7:25       ` Lennart Borgman [this message]
2006-09-13  9:09         ` Jason Rumney
  -- strict thread matches above, loose matches on Subject: below --
2006-09-13 10:01 LENNART BORGMAN

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=4507B26D.7060800@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=cyd@stupidchicken.com \
    --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 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).