unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jeff Clough <jeff@jeffclough.net>
To: GNU Emacs Help <help-gnu-emacs@gnu.org>
Subject: Seeking remote Emacs recommendations
Date: Sat, 05 Aug 2023 09:16:23 -0400	[thread overview]
Message-ID: <86leepvdco.fsf@jeffclough.net> (raw)

Hello!

I'm wondering what people's recommendations are for approaches,
packages, and configurations for running Emacs on a remote GNU/Linux
system and displaying/interacting with that Emacs via Windows 10. I know
there are several ways to accomplish this (or used to be), but I don't
want to bark up an outdated or inefficient tree. Since this has *got* to
be a common need around here, I figured at least one person on the list
would have The Answer.

Various and sundry details of my setup/needs are in the PS.

Thanks!

Jeff

PS...

I have several pieces of Windows-only proprietary software which I
*must* run for my business. Half of these work OK under Wine, most of
the rest have minor instabilities, but one falls over and dies with
alarming regularity. So, Windows 10 Professional is and must remain my
main OS for now.

I also have a machine running Ubuntu 22.04 (desktop) which mostly just
sits around.

This is all on a small, glorified home network where I can set
consistent IP addresses and change any and all settings and software
packages as needed (minus the software dependencies I mentioned above,
of course).

All this said, my main work environment is Emacs. I really can't live
without Org, Gnus, and BBDB at this point. I have all of this *mostly*
working under Windows but I keep running into little...glitches. Most of
these are heisenbugs, and all of them are the sorts of things I've
always seen when running Emacs outside of a *nix environment.

I'm thinking at this point that it might be easier to run Emacs on the
Ubuntu system and display it remotely on Windows. In the Elder Days, I would
have done this via X, and maybe FTP to move files between machines as
needed. This is probably an insane thing to do in 2023.

So, what do *you* do?



             reply	other threads:[~2023-08-05 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05 13:16 Jeff Clough [this message]
2023-08-05 14:03 ` Seeking remote Emacs recommendations Manuel Giraud via Users list for the GNU Emacs text editor
2023-08-05 14:16 ` Sebastian Miele
2023-08-05 17:30 ` Basile Starynkevitch
2023-08-05 22:24 ` John Carter via Users list for the GNU Emacs text editor
2023-08-06 15:59 ` hw

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=86leepvdco.fsf@jeffclough.net \
    --to=jeff@jeffclough.net \
    --cc=help-gnu-emacs@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.
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).