emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to set Emacs as default app on Windows (10)


From: Eli Zaretskii
Subject: Re: How to set Emacs as default app on Windows (10)
Date: Sun, 22 May 2022 12:04:57 +0300

> Date: Sun, 22 May 2022 10:53:42 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> Cc: emacs-devel@gnu.org
> 
> > > >From a DOS box I started the Emacs client adapting the above target:
> > > 
> > > C:\Users\utente>C:\Windows\System32\cmd.exe /c "SET 
> > > path=C:\msys64\mingw64\bin;%path%&& SET PRELOAD_WINSOCK=1&& START /D 
> > > ^"C:\Apps\Emacs\bin^" emacsclientw.exe -c -n -a 
> > > C:\Apps\Emacs\bin\runemacs.exe"
> > 
> > I don't understand why you needed to change that target.  What was it
> > supposed to achieve, and how is that related to the issue at hand,
> > which is setting up the default application to open *.tex files?
> 
> The link above seems to suggest to use emacsclientw which uses runemacs 
> instead to use directly runemacs..

That suggestion doesn't make sense to me, and I think it is unrelated
to your issue and the original question.

> > "Another frame" or "another instance of Emacs"?  How many Emacs
> > processes do you have running after you click on a .tex file in the
> > Explorer?
> 
> I would say: another frame and two processes (from task manager). See the 
> screenshot 

Thanks, but the screenshot doesn't say definitively that there are 2
Emacs processes, it only hints on that (via the warning it shows in
one of the frames).  The definitive answer is to see how many Emacs
processes are shown in Task Manager.

I suspect that what you have is a separate Emacs process, and the
reason for that is that the Emacs session that was already up and
running didn't start the server (via "M-x server-start" or an
equivalent in your init file).

IOW, I think the issue you are having has nothing to do with the
shortcut, it is due to how you customize your Emacs sessions: you
should make sure the server is started there, or else it will be
unable to receive client connections from emacsclient.

> > The tab bar conceptually holds window configurations, not buffers or
> > individual windows.  AFAICT, server.el and emacsclient currently don't
> > have an option to visit files in a new tab, they can only visit it
> > either in an existing frame (the default) or in a new frame, if
> > invoked with the -c command-line option.
> 
> OK, I rephrase the question: How to set Emacs as default app to open .tex, 
> .text, .c. .f90 etc. files similarly to a browser (if Emacs uses tabs...)?
> 
> If it is not implemented you should add it in ToDo list..

If that is what you want, then I suggest to submit a feature-request
bug report, since I don't think we have such a feature.  I think we
will need to implement a new directive in our server-client protocol
to support such a feature.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]