Event JSON
{
"id": "546087f293d2407b83b95c426ef75d98b292ac09f2a6414cb58f15b47f031cac",
"pubkey": "b6e58a4a29d7d8049d01ce5672835b9fcebdcaf22ccb48802874acfea150c7c4",
"created_at": 1718523331,
"kind": 1,
"tags": [
[
"t",
"editors"
],
[
"t",
"emacs"
],
[
"proxy",
"https://graz.social/@publicvoit/112625145033370651",
"web"
],
[
"t",
"vim"
],
[
"t",
"emacsclient"
],
[
"p",
"76408f1d8fabb22a20cfc85bb555d25f4c5180e4239b86b1789d93ca3f4a95b3"
],
[
"e",
"cc821ce66025442b66f80070d7b728cc5d467eb6afe87bd3bd97804180a53fc1",
"",
"root"
],
[
"proxy",
"https://graz.social/users/publicvoit/statuses/112625145033370651",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://graz.social/users/publicvoit/statuses/112625145033370651",
"pink.momostr"
]
],
"content": "I personally prefer #vim for small modifications in text files of all sorts.\n\nNot because #Emacs would be bad for that task.\n\nThe reasons are that I know both environments and my Emacs does all sorts of things during startup.\n\nOn my main host, this would hardly be an issue due to #emacsclient. \n\nHowever, on all other machines (or users), I'd need to have to maintain a ssh-key-chain to transparently use my main Emacs over the network, sometimes multiple hops. That's tedious to me.\n\n#editors",
"sig": "87fb6b645c1a63ef4219d5ccf63dbeb5827ad1ef0563aba2747ead7f169dfe957af64fd2fd860559c626121e2824bf19fe5923a0928c0e132dfccdb732341b14"
}