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/)MI
Posts
1
Comments
38
Joined
2 mo. ago
  • It is a product of its time. If the same research was made 30 years ago, I bet there would be a stark difference to results today. LTO wasn’t as feasible. Compilers were less capable of removing redundant checks. Branch prediction in x86 processors was still a hot new thing. And on top of it all, there was less knowledge about language development.

  • If this was easy, then people would’ve done this a long time ago.

    People have done it. It’s called Edge, Opera, Vivaldi etc. And looking at it historically, Safari is a branch from the same tree as well.

  • Also, nano may not always be installed.

    mcedit, gedit, pico. For majority of people lack of any simple non-vi-based text editor is a corner case not worth worrying about. Definitely not enough of a problem to start ‘How to learn Emacs’ tutorial with ‘Learn Vim’.

  • Why is 0th step of learning Emacs, learning Vim? The whole premiss that you need to know Vim or you’re unable to work on other people’s computers is ludicrous. Nano is perfectly capable editor for the times I need to use computers without Emacs.

  • Admittedly, I’m probably not the best person to ask for recommendation of a noob-friendly distro, but I feel people are overthinking this. If someone produces a list which includes distros I’ve never heard of, I think they spent too much time on ‘Top 10 Noob Friendly Distros in 2025’ websites.

    If you really care about my recommendation, just start with Mint.

    PS. I should also add, this isn’t criticism of you or any other new user who does search online for recommendation. This is more a comment on state of the Internet where there are so many websites which seem to pad their list with obscure distros where really all such articles should give recommendation for one of the same three distributions. Which three I don’t exactly know.

  • src/* will skip hidden files. You want rsync -avAXUNH src/ dst which copies contents of src into dst. Notice the trailing slash in src/. Without the slash, src is copied into dst so you end up with a src directory in dst. The AXUNH enables preserving more things. You might also add --delete if you’re updating the copy.

    PS. I should also mention how I end up with -avAXUNH. Simple:

     undefined
        
    $ man rsync |grep ' -. *preserve'
           --hard-links, -H         preserve hard links
           --perms, -p              preserve permissions
           --executability, -E      preserve executability
           --acls, -A               preserve ACLs (implies --perms)
           --xattrs, -X             preserve extended attributes
           --owner, -o              preserve owner (super-user only)
           --group, -g              preserve group
           --times, -t              preserve modification times
           --atimes, -U             preserve access (use) times
           --crtimes, -N            preserve create times (newness)
    
      

    and then include all that. a covers some of those options and those don’t have to be set explicitly:

     undefined
        
    $ man rsync |grep ' -a ' |head -n1
           --archive, -a            archive mode is -rlptgoD (no -A,-X,-U,-N,-H)
    
    
      
  • I meant what’s the link to use since the same Lemmy post can be viewed through different instances and on each it has a different URL. It’s a bit user-hostile that the link gets you out of your instance (unless you’re on the same instance as author of the post).

  • Yeah, it’s a bit philosophical.

    • In graphical applications, Ctrl+M, Ctrl+J and Return/Enter are all different things.
    • In a terminal in raw mode, Ctrl+M and Return/Enter are the same thing but Ctrl+J is something different. You can for example run bind -x '"\C-j":"echo a"' in bash and Ctrl+J will do something different.
    • In a terminal in canonical mode, they are all the same thing. There probably are some stty options which can change that though.
  • Yes, I agree. But the dispute is what ‘sends EOF’ actually means. The article I respond to claims Ctrl+D doesn’t send EOF but is like Enter except that new line character is not sent. This is, in some sense true, but as I explain also misleading.

  • Linux @lemmy.ml
    mina86 @lemmy.wtf

    Is Ctrl+D really like Enter?

    Response to a recent claim that Ctrl+D in the terminal is like pressing Enter. It kind of is but it’s also misleading to say so without further explanation.

  • You could pass $1 and $got through $(realpath -P -- ...) to make sure all the path are in canonical form. Though now that I’m thinking about it, stat is probably a better option anyway:

     shell
        
    want=/path/to/target/dir
    pattern=$(stat -c^%d:%i: -- "$want")
    find "$HOME" -type l -exec stat -Lc%d:%i:%n {} + | grep "$pattern"
    
    
      
  • You want readlink -f rather than ls -l. ++OK, actually not exactly. readlink won’t print path to the symlink so it’s not as straightforward.++

    Also, you want + in find ... -exec ... + rather than ;.

    At this point I feel committed to making readlink work. ;) Here’s the script you want:

     undefined
        
    #!/bin/sh
    
    want=$1
    shift
    readlink -f -- "$@" | while read got; do
        if [ "$got" = "$want" ]; then
            echo "$1"
        fi
        shift
    done
    
      

    and execute it as:

     undefined
        
    find ~ -type l -exec /bin/sh /path/to/the/script /path/to/target/dir {} +