You haven't lived until you've invoked emacs noninteractively from a Makefile 
to, say... render your documentation
into end user consumables.

On 2/27/19 4:02 PM, Tom Buskey wrote:
> I know the feeling.  I've gotten so used to emacs for coding (python, shell) 
> and vi for remote/quick work that I haven't been able to get into an IDE.
> 
> Mostly I'm writing code on my desktop that will run in a VM or container or 
> the code will build it one of those.  I can't/shouldn't put a whole 
> development envivironment let alone emacs on it and the VM/container is 
> ephemeral.  I'm not sure an IDE would help me much beyond what emacs already 
> has.
> 
> On Tue, Feb 26, 2019 at 8:17 AM Marc Nozell ([email protected] 
> <mailto:[email protected]>) <[email protected] <mailto:[email protected]>> wrote:
> 
>     Like this? Been in base emacs for years.
> 
>     
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Remote-Files.html
> 
>     -marc
> 
>     On Mon, Feb 25, 2019 at 7:00 PM Dan Garthwaite <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>         Bill is correct.  Just stick to:
>         vim scp://target.host.com/.bashrc <http://target.host.com/.bashrc>
> 
>         On Mon, Feb 25, 2019 at 4:32 PM Bill Freeman <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>             Resistance (like capacitance) is futile. Stay with the one true 
> editor. Whatever nifty feature you saw, there is probably an extension to do 
> it in emacs. (Or you can write one.)
> 
>             On Mon, Feb 25, 2019, 2:52 PM Ken D'Ambrosio <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>                 Hi, all.  In Emacs, it's trivially easy to open a file on a 
> remote host:
> 
>                 emacs /user@host:/path/to/file
> 
>                 And while I *do* enjoy Emacs, I admit that some of the other 
> IDE/editors
>                 I've seen look kind of nifty.  But opening files via SSH is 
> really,
>                 really handy -- to the point where I consider it a 
> dealbreaker to not
>                 have it.  I found Visual Code can do SSH, but you have to (at 
> least, by
>                 my reading) set up per-host profiles, etc.  Bleh.  I know 
> that vim can
>                 do it, but I'm just not a vim guy.  I'm just not interested 
> in doing
>                 some out-of-the-box thing like sshmount (or whatever it is).  
> So, at the
>                 end of the day, anyone have an editor they enjoy where it's 
> as easy to
>                 open a file over SSH as it is in Emacs?
> 
>                 Thanks for any thoughts you might have...
> 
>                 -Ken
>                 _______________________________________________
>                 gnhlug-discuss mailing list
>                 [email protected] 
> <mailto:[email protected]>
>                 http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 
>             _______________________________________________
>             gnhlug-discuss mailing list
>             [email protected] 
> <mailto:[email protected]>
>             http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 
>         _______________________________________________
>         gnhlug-discuss mailing list
>         [email protected] <mailto:[email protected]>
>         http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 
> 
> 
>     -- 
>     Marc Nozell ([email protected] <mailto:[email protected]>) 
> http://www.nozell.com/blog
>     _______________________________________________
>     gnhlug-discuss mailing list
>     [email protected] <mailto:[email protected]>
>     http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 
> 
> _______________________________________________
> gnhlug-discuss mailing list
> [email protected]
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> 

-- 
Connect with me on the GNU social network: 
<https://status.hackerposse.com/rozzin>
_______________________________________________
gnhlug-discuss mailing list
[email protected]
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/

Reply via email to