22
Email address for resume
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Mar 2024
22 points (89.3% liked)
CSCareerQuestions
770 readers
1 users here now
A community to ask questions about the tech industry!
Rules/Guidelines
- Follow the programming.dev site rules
- Please only post questions here, not articles to avoid the discussion being about the article instead of the question
Related Communities
- !programming@programming.dev - a general programming community
- !no_stupid_questions@programming.dev - general question community
- !ask_experienced_devs@programming.dev - for questions targeted towards experienced developers
Credits
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
Why do you type with
random parts
split by carraige
return.
It makes me read it like Captain Kirk.
Haha yeah I've written a fediverse system which connects email and activitypub. Writing these from my regular email client (more info if interested: https://apubtest2.srcbeat.com/apas.html) Looks like what I'm gonna do is delete all carriage returns out just before it's sent out to the fediverse. Thanks for spotting that!
Out of curiosity from which app/client/frontend did you notice this?
On lemmy for iPhone you’re just skipping spaces “randomly” (where your carriage returns are, I’m guessing). It looks like:
Sorry not sure which app that is. Is this the default web interface e.g. at https://programming.dev ?
Or Memmy or one of the apps from the app store?
Memmy, sorry.
what client are you using? i dont think most render single linebreaks
Ah good spot. Sync for Lemmy renders the new lines.
Still don't know why they are there in the first place :)
perhaps habit? i know many people write markdown documents that way, it can help with editors which dont wrap text, and may be better for using
grepand related line-based tools.Ah so if you really want to know, it's because one of the mail clients I use quoted-printable encodes the body when sending a message with lines >80-ish characters.
I haven't implemented a decoder on the other end. My current workaround is to pipe everything through fmt before it goes out.
Yes I also actually do this too; I'm a fan of semantic line feeds.
In case you couldn't tell, the whole system is a WIP ;)
:-)