summaryrefslogblamecommitdiffstats
path: root/2022/talks/tramp.md
blob: cf7b5076215b63b643b6218c0bcd47c2070dda48 (plain) (tree)
1
2
3
4
5
6
7
8
9
                       







                                                                                                     
                                                                         
                                                                                                                                                                                                                     
















                                                                           
[[!sidebar content=""]]
[[!meta title="Elisp and the TRAMP: How to NOT write code you don't have to"]]
[[!meta copyright="Copyright © 2022 Grant Shangreaux"]]
[[!inline pages="internal(2022/info/tramp-nav)" raw="yes"]]

<!-- Initially generated with emacsconf-generate-talk-page and then left alone for manual editing -->
<!-- You can manually edit this file to update the abstract, add links, etc. --->


# CANCELLED: Elisp and the TRAMP: How to NOT write code you don't have to
Grant Shangreaux (Shang-groo or Shang-grow, he/him, <mailto:shoshin@cicadas.surf>, <https://cicadas.surf/~shoshin>, IRC: shoshin on libera.chat, @kheya@mastodon.social, <https://matrix.to/#/@shoshin:cicadas.surf>)

[[!inline pages="internal(2022/info/tramp-before)" raw="yes"]]

When you have a hammer, everything looks like a nail. When you have
Emacs, everything looks like&#x2026; what? This is a story of understanding
a particular feature of Tramp and realizing it could be used in all
sorts of places in Emacs-land. Some of them are truly useful, but I
ended up in a place where applying it was going to create a non-trivial
amount of work writing Emacs Lisp to extend EMMS.



[[!inline pages="internal(2022/info/tramp-after)" raw="yes"]]

[[!inline pages="internal(2022/info/tramp-nav)" raw="yes"]]