this post was submitted on 31 Jul 2023
1 points (66.7% liked)

Emacs

342 readers
1 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (8 children)

interesting. mastodon.el also uses plstore, so if it works (saving your credentials) your machine's encryption should be working. but the auth process for the two services is totally different, so I had to write the lem.el auth code from scratch. I can take a look at it v soon, I'm keen to have any auth issues sorted out asap.

it'd help if you cd describe when the error message appears, or what exactly you do that causes it.

actually a backtrace would be most useful to track down the error.

you cd also try opening the plstore file in your .Emacs.d folder and encrypting / decrypting it.

thanks!

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (5 children)

I can see posts in lem! I guessed correctly that issue with GPG was that it really, really wanted a tty, so I tried logging in from emacs -nw and that worked. Once the credentials are stored I can use lem from GUI Emacs! Apparently I need to install some markdown executable... I faked it with ln -s /bin/cat ~/bin/markdown and everything is hideous but useable! 😛

I tried posting this comment from lem and it seemed to work but I can't seem to see it here, so I'm posting again from the browser. I'm getting closer and closer to lem working and am very excited.

EDIT: spoke too soon, now I get DEcryption errors even in emacs -nw. Maybe I'm out of my depth here.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (4 children)

that's interesting and also pretty frustrating. i didn't think i'd encounter such issues using plstore. are you able to provide a backtrace for the error? it'll show what is calling the encryption functions, and there could be an error before the one displayed. also try manually opening the .plstore file in your .emacs.d directory and encrypt and decrypt it while open. maybe you do just have some plstore problems. / btw, lemmy and lem.el require markdown, so best to install it. the latter requires markdown-mode too.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (1 children)

I'll post a back trace later. I understand the dependence on markdown-mode, but why also an external markdown executable? You could just let markdown-mode fontify the text and people can hide the markup symbols if they like. I use markdown-mode a lot and it never once occurred to me that I needed a markdown converter.

EDIT: Things seem to be working now that I have epg-pinentry-mode set to 'loopback, so I won't post the backtrace after all.

[–] [email protected] 1 points 2 years ago (1 children)

glad you got going!

thanks for opening issues in the repo.

bindings are just work to do. development moving v fast, mainly I'm just still trying to add basic features. eg posting is only 4 days old.

I'm not sure about the markdown issue, I just require markdown-mode. mayb I use a fn in the mode that requires the binary.

Lemmy uses markdown, so to render post content I take the markdown data, render it using markdown-mode, then render the HTML output.

not sure how else to do that, nor how to not rely on markdown mode.

I shd look into it more, but mainly I had to just find my own way, as Lemmy is hardly documented at all.

feel free to make more requests, its easier than fumbling along alone.

[–] [email protected] 1 points 2 years ago

yeah actually, rendering markdown is what requires the binary

load more comments (2 replies)
load more comments (2 replies)
load more comments (4 replies)