26

Looks to be a UK only thing, but still very cool.

1
23
12
1
1
2
6
pre-commit with Django (learndjango.com)
1
17
2
1
[-] jnovinger@programming.dev 1 points 3 years ago

Looks like at least inline code styling is working in titles: https://programming.dev/post/184949. I also confirmed elsewhere that emojis work in titles.

I went looking at the Lemmy docs, but didn't find anything specific about titles. Just this:

The main type of content in Lemmy is text which can be formatted with Markdown. Refer to the table below for supported formatting rules.

[-] jnovinger@programming.dev 1 points 3 years ago

I'm curious about Markdown in post titles. Anybody know about that?

[-] jnovinger@programming.dev 1 points 3 years ago

Thanks @forkball@lemmy.world , I think I was just in the right place at the right time.

I'll see if I can dig up some old technical blog posts from work. On my current project, we're using Python for a research SaaS tool for sports information people, generally at broadcasters and league offices. We also have a fair amount of ETL type code in Python for aggregating and enriching data.

[-] jnovinger@programming.dev 1 points 3 years ago

I used Lemmy's cross-post functionality, but it doesn't seem to have marked it?! Original post is https://lemmy.ml/post/1213162

[-] jnovinger@programming.dev 1 points 3 years ago

I raise you

@lambda _: _()
def result() -> int:
    global a; global b; a, b = b, a

hat tip to @sisyphean@programming.dev via Cursed Python

[-] jnovinger@programming.dev 1 points 3 years ago

Derp, it's the 19th, not the 20th! 🤦

I guess I'll leave this up for today and tomorrow at this point.

[-] jnovinger@programming.dev 1 points 3 years ago

Is this the book we're talking about?

https://doc.rust-lang.org/book/

[-] jnovinger@programming.dev 1 points 3 years ago

Hey @chaoticAnimals@programming.dev , I can't answer that specific questions, as I don't generally do anything with Java or Assembly. However, vim/neovim's ability to target features base on filetype is really helpful. It means that you can configure any particular plugin or feature to only work with *.py files, which is the python filetype in neovim.

I started with vim a long time ago and migrated to neovim a couple of years ago, so my personal configuration is kind of all over the place. With vim, I used things like python-mode which is all-in-one sort of Python plugin for vim.

Recently, on neovim, I've switched that out to use a Language Server Protocol plugin, like neovim/nsm-lspconfig for overall LSP configuration and language specific LSP servers, like python-lsp-server for Python.

You can get the LSP stuff for Python going by following the directions in neovim/nsm-lspconfig's README and in the projects server_configurations.md. server_configurations.md also contains tips for many other language/project specific LSP servers.

I'll see if I can boil my current config down to a minimum for LSP stuff later and post a link.

[-] jnovinger@programming.dev 1 points 3 years ago

I couldn't agree more!

I had a great colleague at my previous job, who was great at reminding folks that we're there to get things done together and struggling in silence was the opposite of that. If you can't figure it out after an hour, give someone (anyone!) a holler and get a second opinion.

view more: ‹ prev next ›

jnovinger

0 post score
0 comment score
joined 3 years ago
MODERATOR OF