• 0 Posts
  • 13 Comments
Joined 11 months ago
cake
Cake day: December 1st, 2023

help-circle

  • rien333@lemmy.mltoLinux@lemmy.mlHow to quit VIM?
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 months ago

    Some people over at reddit seem to suggest that the functionally you speak of doesn’t exist, except in the form of a proof of concept snippet over at SO.

    EDIT: Said snippet would probably be sufficient, if it handled codeblocks correctly (stuff in between ```). At the moment, it handles them miserably (maybe because they are multineline elements?)


  • rien333@lemmy.mltoLinux@lemmy.mlHow to quit VIM?
    link
    fedilink
    arrow-up
    2
    ·
    3 months ago

    No joke, Emacs has the ability to render in line markdown, essentially the current line is just text, while the rest of the doc is rendered as markdown titles, links, lists, etc.

    This sounds amazing. I’ve been using markdown-mode for ages now though, and I’ve never come across this feature.

    How do you enable this?




  • One thing that hasn’t been mentioned yet is interopability, that is, flatpak interacting with the rest of your system.

    I’m not that familair with flatpak, but in my brief experience with the steam flatpak, I had trouble getting it to recognize my controllers. Steam installed through pacman (Arch’s package manager) had no such issues, on the other hand. My hunch is that this has to with flatpaks being more isolated from the rest of your system.

    Im pretty sure that’s just some kind of permission issue, but it can be nice to not have to troubleshoot acces rights and the like. But this is obviously a double edged sword: more isolation may also mean more security, just at the cost of ease of interaction with other components.



  • There’s a compability layer, generally called pipewire-pulse. I think it’s not a one-for-one copy, but it works great for desktop applications that expect pulse.

    Some things that previously were pulseaudio modules, like rtp and raop (airplay), have been reimplemented as native pipewire modules, I believe.

    More complicated setups I can’t personally speak to, but since pipewire is also catered towards professional audio workflows (as opposed to just desktop audio), you should at least be able to replicate what you have now.

    And, as others have already pointed out, pulseeffects has been long dead, and now lives on as easyeffects.