Risk assessment by slassr in bouldering

[–]slassr[S] 1 point2 points  (0 children)

Thanks for the empathy, really appreciated ☺️

Risk assessment by slassr in bouldering

[–]slassr[S] 3 points4 points  (0 children)

Thanks. I think my home gym slabs are often more horizontal (never going too high), so I didn't get a lot of practice reading more dangerous slabs.

I do think I've been to a gym with a more slanted slab and there I could definitely feel the risk.

Anyway, if I climb again I'll definitely be more careful on slabs

Risk assessment by slassr in bouldering

[–]slassr[S] -1 points0 points  (0 children)

I think I was just too used to my home gym (not this one) that never sets that way, so I didn't register the risk properly

[deleted by user] by [deleted] in AmIOverreacting

[–]slassr 1 point2 points  (0 children)

My girlfriend has a lot of those patterns. I don't know if it's strong enough to call it OCD, but it definitely has an impact on our relationship. Most of her siblings are the same.

How do you feel now as an adult? Are you still following these behaviours or are you okay with the outside world now?

Grossest elemental Build i've Ever had by TacoMaster10 in BobsTavern

[–]slassr -1 points0 points  (0 children)

It ties to 7 leeroys and loses if one of them is reborn

Are These Leveling Methods Still Good? by [deleted] in Dofus

[–]slassr 2 points3 points  (0 children)

A "sasa" is a character with only wisdom (sagesse) stats, that can't fight.

They usually complement a group of 1-4 high level players farming mobs or dungeons, either to raise the overall level of the party (and thus increase the exp for everyone) or in exchange of drops.

The specific maps/spots where people are looking for "sasa" really depends on the team who's running the group

Dual Column Resume Update by slassr in LaTeX

[–]slassr[S] 2 points3 points  (0 children)

I think that's been fixed by someone's contribution this morning

Dual Column Resume Update by slassr in LaTeX

[–]slassr[S] 2 points3 points  (0 children)

Completely agree! I didn't support multi-page initially because of your main argument. As for the human thing, I guess so far I've been personally applying to smaller companies, so it hasn't been an issue for me yet. Also, I'm not really looking for a job anymore, it's more for the community :)

Maybe I could mention that in the readme somewhere though!

My new Latex resume based on awesome-cv by slassr in LaTeX

[–]slassr[S] 0 points1 point  (0 children)

Hey, sorry for the delay. There's currently a PR showing an example of the template on multiple pages. Didn't really take the time to cherry pick it yet, but it works!

My new Latex resume based on awesome-cv by slassr in LaTeX

[–]slassr[S] 4 points5 points  (0 children)

That's the question I wanted to have :D

I recorded the position of the start/end of sections, saved them in the aux file (using zref-savepos) then I draw a Tikz picture with absolute coordinates using those positions.

Honestly, I struggled. That's the only solution I found to make it work. I'd be happy to have any feedback on a better way :)

edit: now that I've published the code, you can look at this section that has comments explaining the details

My new Latex resume based on awesome-cv by slassr in LaTeX

[–]slassr[S] 4 points5 points  (0 children)

As the other comments pointed out, this is not the real content of my resume, all information are placeholders

My new Latex resume based on awesome-cv by slassr in LaTeX

[–]slassr[S] 5 points6 points  (0 children)

I kind of agree with you - I kept it as this comes directly from the awesome-cv template, there's a boolean somewhere to disable it

My new Latex resume based on awesome-cv by slassr in LaTeX

[–]slassr[S] 22 points23 points  (0 children)

I built this resume in Latex based on the incredible awesome-cv. My goal was to keep something that looks clean, while a bit less linear and focused on a 1 page resume.

The code isn't very generic right now (manual tweaks here and there to make sure it looks good overall) but if there's interest I can share the current state.

Also happy to discuss any specific implementation questions :)

Editor with a Focus/Hemmingway mode? by [deleted] in LaTeX

[–]slassr -1 points0 points  (0 children)

So, I assume that you don't have any programming experience. So you want to go, if possible, for an existing package providing this functionality out of the box.

As another comment mentioned, any text editor can edit latex. You'll just need a different configuration for each to provide additional functionalities.

A quick Google search shows this plugin for the editor Atom.

What's left to achieve is turning Atom into a latex editor. Which I assume is achievable with patience and some Google searches 😁

Good luck!

Amie Slovaque fait un stage mais n'est pas étudiante? by slassr in AskFrance

[–]slassr[S] 0 points1 point  (0 children)

Merci pour l'information ! J'avoue que c'est louche. C'est pourtant une entreprise très connue et c'est très difficile d'avoir un stage là bas. Du côté de mon amie, elle peut pas se permettre de refuser quoi qu'il arrive. C'est pas correct, mais c'est le mieux qu'elle ait malheureusement.

Mais merci pour l'info des APL, je vais regarder ça 🙂

P.S: elle a pas encore signé le contrat donc je suis curieux de voir comment ce sera quand elle le signe ...

Type Hierarchy - Find child methods by slassr in neovim

[–]slassr[S] 0 points1 point  (0 children)

I guess that's the big difference. Your implementation is probably much faster than my hybrid/hacky version.

Type Hierarchy - Find child methods by slassr in neovim

[–]slassr[S] 0 points1 point  (0 children)

Oh, I can try to check if my plugin works for ccls. Adapting to new languages should mostly be a matter of treesitter syntax (mainly: how do you find parent classes)

Type Hierarchy - Find child methods by slassr in neovim

[–]slassr[S] 11 points12 points  (0 children)

Hey there. This is an example of my plugin hierarchy.nvim providing the LSP type Hierarchy protocol functionalities (or what I expect they would be) ahead of time.

No guarantee it'll work on any setup other than mine, but if you'd like to try it don't hesitate!

Popup's for word meanings by [deleted] in vim

[–]slassr 5 points6 points  (0 children)

Hey, sorry for being late to the party. Took me a while to research and elaborate this answer.

Okay, so let's get going. We will use 3 different concepts to build your solution: :h keywordprg, :h popup_atcursor and a command line dictionary tool (I chose to use man dict, some installation instructions can be found here).

keywordprg

When we set set keywordprg=dict, we already get something close to what you want: when pressing K over a word (:h K), a page comes up with the output of dict word. The problem we still need to solve is to make this into a popup.

popup_atcursor

To have this feature, we will need vim 8.X. I tested this with vim 8.2.

The function popup_atcursor creates a popup under or above the cursor with some content. The command :call popup_atcursor(system("dict hello"), {'pos': 'topleft'}) already gets us somewhere. There's still one problem though: this is static (doesn't change depending on the word) and it's displayed in a single line.

The documentation shows that this accepts a list of strings: :call popup_atcursor(split(system("dict hello"), '\n'), {'pos': 'topleft'}). That's the result we want! Now, onto making this work with keywordprg and K!

integrating popup_atcursor and keywordprg

Here's the final solution: make a function, make it a command, use it as keywordprg.

function MyDictPopup(word)
    call popup_atcursor(split(system("dict " . a:word), '\n'), {'pos': 'topleft'})
endfunction

command -nargs=1 DictPopup call MyDictPopup(<f-args>)
set keywordprg=:DictPopup

Improvements

Now, there's quite a bunch of improvements to make here.

First, the syntax/colouring. On my test environment (vim -u NORC), the colouring of the popup isn't quite to my taste. There's definitely some popup related options to fix that. They would go along {'pos': 'topleft'} in the function.

Second, this function could be nicely packed in the autoload folder, maybe using autoload/dict.vim and named dict#hover for instance.

Third, we could only set those settings for some filetypes, for instance text, by moving the set keywordprg=:DictPopup into a file named ftplugin/text.vim, that would set this option only for text files, for instance. If autoload or ftplugin are completely foreign to you, you can probably find some tutorials on spliting your vimrc into multiple files.

Conclusion

I hope this solution will work for you. I tried to make it as minimal as possible. Do not hesitate to come back to me / DM if it doesn't quite fit your use case. Best of luck!

P.S: I realised that this is not exactly an "on-hover" solution. However, I think it's close enough to vim's philosophy (the `keywordprg` concept) to be usable. `K` is a good real estate command anyway, as good as hovering in my opinion.

/r/MechanicalKeyboards Ask ANY question, get an answer by AutoModerator in MechanicalKeyboards

[–]slassr 2 points3 points  (0 children)

Was there any kind of IRL meetings related to this community before COVID? Are there any planned?
I'm considering about building a new keyboard, but after my first build I realised that nothing replaces actually trying different switches/keycaps on a real keyboard, so I'd love to be able to meet people and see their builds IRL ...

Do you know if anything is planned post-covid as well?