If I really want to shave a GNU Emacs yak, I could try sorting out TRAMP, which is a complete mess because I use a non-standard shell and shell environment.
-
If I really want to shave a GNU Emacs yak, I could try sorting out TRAMP, which is a complete mess because I use a non-standard shell and shell environment. But, you know, I don't need remote editing that much.
It's not that yak has too much hair. It's that its extremely tough, entangled hair. With thorns.
-
If I really want to shave a GNU Emacs yak, I could try sorting out TRAMP, which is a complete mess because I use a non-standard shell and shell environment. But, you know, I don't need remote editing that much.
It's not that yak has too much hair. It's that its extremely tough, entangled hair. With thorns.
I am (a) curious about your shell environment and (b) curious how you normally are connecting to remote systems such that TRAMP is working right.
-
I am (a) curious about your shell environment and (b) curious how you normally are connecting to remote systems such that TRAMP is working right.
@rk I use rc¹, which is not sh compatible in syntax. On some systems I run it directly as my /etc/passwd shell, on others I use a minimal /bin/sh environment that execs it on .profile startup. TRAMP is ... unhappy.
My usual 'remote editing' approach with Emacs is 'ssh -X machine; emacs ... &'. If I don't care enough to have Emacs fully set up (which is most machines), I use vi(m). Often I use vi(m) anyway.
-
@rk I use rc¹, which is not sh compatible in syntax. On some systems I run it directly as my /etc/passwd shell, on others I use a minimal /bin/sh environment that execs it on .profile startup. TRAMP is ... unhappy.
My usual 'remote editing' approach with Emacs is 'ssh -X machine; emacs ... &'. If I don't care enough to have Emacs fully set up (which is most machines), I use vi(m). Often I use vi(m) anyway.
@rk TRAMP probably works great on all of the systems I don't care enough about to have gone to the bother of setting up rc and I'm just using bash as a login shell. Unfortunately those are also the systems where I normally don't have anything I want to edit.
-
@rk I use rc¹, which is not sh compatible in syntax. On some systems I run it directly as my /etc/passwd shell, on others I use a minimal /bin/sh environment that execs it on .profile startup. TRAMP is ... unhappy.
My usual 'remote editing' approach with Emacs is 'ssh -X machine; emacs ... &'. If I don't care enough to have Emacs fully set up (which is most machines), I use vi(m). Often I use vi(m) anyway.
I do like rc
-
@rk TRAMP probably works great on all of the systems I don't care enough about to have gone to the bother of setting up rc and I'm just using bash as a login shell. Unfortunately those are also the systems where I normally don't have anything I want to edit.
@rk When TRAMP actually works it can do some spooky impressive things. I just TRAMP'd off to my FreeBSD test machine, started magit, pulled an update to a program¹, started a (Go) LSP server, and compiled the program, all remotely. Of course it probably would have been faster to SSH to the machine to do 'git pull; go build', but whatever. It's not that the bear dances beautifully, it's that it dances.
-
If I really want to shave a GNU Emacs yak, I could try sorting out TRAMP, which is a complete mess because I use a non-standard shell and shell environment. But, you know, I don't need remote editing that much.
It's not that yak has too much hair. It's that its extremely tough, entangled hair. With thorns.
One of my GNU Emacs TRAMP issues turns out to be that not only do I have a non-standard shell, it has a non-standard prompt that TRAMP doesn't recognize.
This is my face about wrestling with GNU Emacs regular expressions.
-
One of my GNU Emacs TRAMP issues turns out to be that not only do I have a non-standard shell, it has a non-standard prompt that TRAMP doesn't recognize.
This is my face about wrestling with GNU Emacs regular expressions.
This is my face when TRAMP absolutely requires your normal remote shell to accept backslash quoting of '#' and '$'. This fails spectacularly on my shell, of course.
-
This is my face when TRAMP absolutely requires your normal remote shell to accept backslash quoting of '#' and '$'. This fails spectacularly on my shell, of course.
On the positive side, writing GNU Emacs regular expressions with rx is quite pleasant and thankfully TRAMP was already using rx for the regexp I had to change (augment). Not that augmenting it to recognize my shell's prompt was useful by itself, because of that whole backslash quoting thing.
-
On the positive side, writing GNU Emacs regular expressions with rx is quite pleasant and thankfully TRAMP was already using rx for the regexp I had to change (augment). Not that augmenting it to recognize my shell's prompt was useful by itself, because of that whole backslash quoting thing.
This is my face when setting tramp-remote-path appears to do exactly nothing to change how Eglot doesn't find 'gopls' anywhere. And it's not using my local $PATH, either. TRAMP and/or Eglot search some apparently hard coded list of things and give up, since said list includes nothing in $HOME.
-
This is my face when setting tramp-remote-path appears to do exactly nothing to change how Eglot doesn't find 'gopls' anywhere. And it's not using my local $PATH, either. TRAMP and/or Eglot search some apparently hard coded list of things and give up, since said list includes nothing in $HOME.
And now tramp-remote-path appears to work for me. No, I don't get what's going on, but I'll take it.
Also, it would be nice if I could make '(use-package tramp ...)' work and let me automatically apply hooks and changes when TRAMP first activates, but not so far, so I'll have to remember to run a magic customization command when I care.
Do I really understand what I'm doing with GNU Emacs? Not always.
-
And now tramp-remote-path appears to work for me. No, I don't get what's going on, but I'll take it.
Also, it would be nice if I could make '(use-package tramp ...)' work and let me automatically apply hooks and changes when TRAMP first activates, but not so far, so I'll have to remember to run a magic customization command when I care.
Do I really understand what I'm doing with GNU Emacs? Not always.
Actually tramp-remote-path appears to work some of the time and not work some of the time and do I know why? No, no I do not.
-
Actually tramp-remote-path appears to work some of the time and not work some of the time and do I know why? No, no I do not.
Current status: I would like to set some combination of TRAMP and GNU Emacs ELisp on fire with the power of my mind because something that by all rights ought to be working is absolutely not working (ie, tramp-remote-path). Does TRAMP provide any *useful* debugging information for this failure? Lol no, of course not, it silently does something but even on verbosity 9, that something is opaque.
And people ask why I don't appreciate the wonders of TRAMP. This. This is why.
-
Current status: I would like to set some combination of TRAMP and GNU Emacs ELisp on fire with the power of my mind because something that by all rights ought to be working is absolutely not working (ie, tramp-remote-path). Does TRAMP provide any *useful* debugging information for this failure? Lol no, of course not, it silently does something but even on verbosity 9, that something is opaque.
And people ask why I don't appreciate the wonders of TRAMP. This. This is why.
@cks Combinatorial explosion
-
This is my face when TRAMP absolutely requires your normal remote shell to accept backslash quoting of '#' and '$'. This fails spectacularly on my shell, of course.
-
@JdeBP A version of the Plan 9 rc, which has much, much simpler quoting that is decisively different.
(' ... ' quotes everything, '' inside is a single '.)
-
@JdeBP A version of the Plan 9 rc, which has much, much simpler quoting that is decisively different.
(' ... ' quotes everything, '' inside is a single '.)
I wondered whether it would be that. I couldn't think of much else as a possibility. Even the Thompson shell unescapes \$ .
-
Current status: I would like to set some combination of TRAMP and GNU Emacs ELisp on fire with the power of my mind because something that by all rights ought to be working is absolutely not working (ie, tramp-remote-path). Does TRAMP provide any *useful* debugging information for this failure? Lol no, of course not, it silently does something but even on verbosity 9, that something is opaque.
And people ask why I don't appreciate the wonders of TRAMP. This. This is why.
On the positive side, I think I have my GNU Emacs TRAMP issues figured out, although not necessarily solved. I'm going to have to write a techblog entry about this (which will inevitably improve my understanding and illuminate dark corners, and which may be hysterically wrong in parts because I'm using an irritated chainsaw here).
I should not really have to read tramp.el to figure things out.
-
On the positive side, I think I have my GNU Emacs TRAMP issues figured out, although not necessarily solved. I'm going to have to write a techblog entry about this (which will inevitably improve my understanding and illuminate dark corners, and which may be hysterically wrong in parts because I'm using an irritated chainsaw here).
I should not really have to read tramp.el to figure things out.
@cks So you've tramp.elled it into submission?
-
R relay@relay.mycrowd.ca shared this topic
