Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)O
Posts
0
Comments
20
Joined
3 yr. ago

  • It's likely a private/internal project, so you need to log in to prove you are allowed access. The same thing happens for one of my personal private projects.

    Edit: After logging in, the URL you posted 404's.

  • Mine looks like this:

    So it should be possible, at least for the parameters.

     
        
    - clangd (id: 3)
      - Version: clangd version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261) linux+grpc x86_64-unknown-linux-gnu
      - Root directory: ~/repos/traffic-generator
      - Command: { "clangd", "--clang-tidy", "--enable-config", "--compile-commands-dir=build" }
      - Settings: {}
      - Attached buffers: 134
    
      

     yaml
        
    ---
    Diagnostics:
        UnusedIncludes: Strict
        MissingIncludes: Strict
        ClangTidy:
          FastCheckFilter: None
          Add:
            - bugprone-*
            - cert-*
            - clang-analyzer-*
            - clang-diagnostic-*
            - concurrency-*
            - misc-*
            - modernize-*
            - performance-*
            - portability-*
            - readability-*
          Remove:
            # - readability-redundant-member-init
            - bugprone-easily-swappable-parameters
            - readability-identifier-length
            # - readability-function-cognitive-complexity
    
    CompileFlags:
      Add: [-xc]
      Remove: [-fanalyzer]
    
    Completion:
      AllScopes: true
    
    InlayHints:
        Enabled: No
    
    SemanticTokens:
      DisabledKinds: []
      DisabledModifiers: []
    ...
    
      
  • 100 % agree. I don't mind developers asking for donations, but this seemed too intrusive. Especially with the 20-second timeout to dismiss it. The developer also seemed to have a bit of an attitude in their response.

  • Oh awesome, thanks for sharing!

  • I think the name initially referred to WINdows Emulator and was later changed, though I can't find a good source for it. I wonder why they insist on not calling it an emulator.

  • 1. Where do you find what shows/films to watch?

    I don't discover it any certain way but once I know what I'm looking for I just search in qbittorrent. For anime I have RSS feeds set up.

    2. Do you stream for convenience or download for superior quality?

    I download.

    3. Where do you store media?

    Internal storage, currently some SSDs.

    4. What software are you using to watch it?

    mpv + fsr/Anime4K shaders.

    5. How do you keep track of your watchlist, which episode you already watched or where you left off in a movie?

    I use trackma/taiga with MAL for anime, for regular shows/movies I don't use anything.

  • Codeberg looks pretty good at a quick glance.

  • You're not wrong, but it bugs me when my ratio drops, so I always seed everything I download. I have a pretty good internet service though.

    My stats:

  • Linux uses 8 spaces. Excerpt from the official style guide:

    Tabs are 8 characters, and thus indentations are also 8 characters. There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3.

    Rationale: The whole idea behind indentation is to clearly define where a block of control starts and ends. Especially when you’ve been looking at your screen for 20 straight hours, you’ll find it a lot easier to see how the indentation works if you have large indentations.

    Now, some people will claim that having 8-character indentations makes the code move too far to the right, and makes it hard to read on a 80-character terminal screen. The answer to that is that if you need more than 3 levels of indentation, you’re screwed anyway, and should fix your program.

    In short, 8-char indents make things easier to read, and have the added benefit of warning you when you’re nesting your functions too deep. Heed that warning.

    The reasoning seems sound, but I still prefer 4 personally.

  • Oof, that's annoying.

    Weird that :syntax off doesn't work, from a small test it seems to do the trick for me. But I guess as long as vim works there's no need to replace it 🙂

  • Try running this: :set indentexpr= and then :set noautoindent. Without any config file, this works for me while in a makefile that looks like this:

     makefile
        
    foo: foo.c bar.h
            $(CC) $< -o $@
    
      

    The indentexpr option is set by filetype, but disabling filetype indent after already opening a makefile is too late, it would need to happen before opening it (in either a config file or directly after running nvim without any file specified).

    However, indentexpr seems to only control the automatic indentation when hitting enter at the target line, but not within the recipe for it. To fix that I also had to disable autoindent.

  • Ah dang, you're right, I must have read it too quickly. Yeah then I also think it's something about not loading the config, it can be investigated by checking the runtime values like I described in my second edit.

  • Using a the ubuntu 24.04 docker image for testing, I was able to disable automatic indentation with this config in ~/.config/nvim/init.lua:

     lua
        
    vim.cmd("filetype indent off")
    
      

    If you prefer using vim syntax it would instead be the following in ~/.config/nvim/init.vim:

     vim
        
    filetype indent off
    
    
      

    Note: it seems this file is not loaded if a init.lua file is present in that directory

    Edit to add: So the reason this is required is, similar to vim (so you may already be familiar with this), there are filetype-specific configurations loaded. These usually reside in /usr/share/nvim/runtime/<plugin/indent/syntax/etc>/<filetype>. You can configure what files to load using the :filetype command.

    There's more info here: https://neovim.io/doc/user/filetype.html

    Second edit: Also when filetype indent/plugin/syntax is on, it seems to be loaded after your user config, so it overrides it. You can investigate if your actual config was applied or not by running, for example, :set autoindent? or :set cindent?. If the values do not match your configuration, it was likely overridden by :filetype. This was the case for me.

  • Gotcha. That's actually good because it will be easier to troubleshoot. I will try to reproduce in a barebones config and see if I can figure something out. What language are you editing, and what version of neovim do you use? Distro may also be relevant in case they package some indent.vim file(s).

  • Are you using treesitter? I think that has an option to handle indentation, but I'm not sure if it's enabled by default.