Skip Navigation

Posts
16
Comments
396
Joined
3 yr. ago

  • Yes, they are reverting back. Fedora users always live on the edge. They are basically (but not quite right) "always" the first accepting a new technology. Not even Archlinux does that. Arch users obviously live on the edge too, but for other reasons. :D

    But wasn't Fedora not going to discontinue X11 support only for GNOME version? I thought other spins are still allowed to support it, but doesn't matter anymore, because they reverting this idea back. I think. But why didn't you switch to another distribution, instead buying new hardware, if that was the only problem?

  • A dash is a bit problematic from practical point of view. In example I allow single numbers without a colon like just 6 which would be interpreted as 6:6. And each element is optional as well, which would make -6 either be a negative number, an commandline option or a range? Some languages also use dots .. instead. If I want ever support negative numbers, then the hypen, dash or minus character would be in the way.

    I mean I could just do a duck typing like stuff, where I accept "any" non digit character (maybe except the minus and plus characters) with regex. Hell even a space could be used... But I think in general a standardized character is the better option for something like this. Because from practical point of view, there is no real benefit for the end user using a different character in my opinion. Initially I even thought about what format to use and a colon is pretty much set in stone for me (Edit: this part didn't age well) I recently switched to .. after long thinking.

  • Fedora even switched to Wayland by default in 2016 (at least for the GNOME release). I don't know what they were thinking. 8 to 9 years before they were already using Wayland... and it still have some "problems". Can't imagine what you were going through. :D

    But compared to Fedora, Ubuntu only did change temporarily to Wayland right? I mean it was not an LTS version. I installed LTS 18.04 and don't remember anything like that by default.

  • Those who don't care, don't have anything to say and should not the deciding factor. Why count voices who don't care?

  • Who "promoted" it as superior to X11? Pretty much everyone I watch and read said that Wayland had their problems and they are working on it, but it is the future. There are ideas and concepts that are superior to X11, but it does not mean its fleshed out. I don't think anyone said that Wayland is superior to X11 in every aspect. Not even the most die hard fan say it. :D

  • It doesn't need to be. The goal is not to recreate and be compatible with X11, otherwise it would defeat the idea to create something new. Wayland is here, because it needs to do things differently. It's the same as Linux operating systems will never be ready for every Microsoft user. And that's okay.

  • Nothing changes much, its just the elements are all from top to down now and wider. I liked the old one more, where I had to less scroll. This new layout is more smartphone focused with vertical layout, while I use my big pc screen with horizontal layout. It's just not good. The only positive side is, it looks less cluttered and it is straightforward.

  • I think that I'm going with these approaches. For the '0', I'm now accepting it as the 0 element. Which is not 0 based index, but it really means before the first element. So any slice with an END of 0 is always nothing. Anything that starts at 0 will basically give you as many elements as END points to.

    • 0: is equivalent to : and 1: (meaning everything)
    • 0 is equivalent to 0:0 and :0 (meaning empty)
    • 1:0 still empty, because it starts after it ended, which reads like "start by 1, give me 0 elements"
    • 1:1 gives one element, the first, which reads like "start by 1, give me 1 element"

    I feel confident about this solution. And thanks for everyone here, this was really what I needed. After trying it out in the test data I have, I personally like this model. This isn't anything surprising, right?

  • Now that you ask, I don't have any example of this. I know program head has negative numbers to access from the last element backwards ls -1 | head -n -1, but it does not start by 0. So yeah, the 0 as last element might be not as common as I thought to be.

  • No, that's not an option here. This is a commandline program, something like grep in example. And this slice is just one of the many features the user could use to refine the output.

  • But contrary to that, often '0' is also used as the last element or points to "the entire match" in example. Whatever that is. I feel like outside of programming languages, for the end user, its not that clear of an answer. Why I created this topic.

    I'll read the linked article and rethink this topic. Maybe introducing another option to make the index 0 based (or the other way 1 based).

  • First, thanks for the answer. As for the user base, its actually gaming oriented and they typically do not interact with 0 base. So I guess that makes for an obvious choice. And at the moment its also "inclusive". To get one element user needs to 2:2. If user gives only one element, such as 2, then I could convert it into 2:2, to get one element. Sounds logical, right? Sorry for having so many follow up questions, my head is currently spinning.

    Do you think this interferes somehow with the logic of a "missing" slice element, which would default to "the rest of the list". In example 2: would then get the second element and until rest. This is the default behavior in Rust.

    If I have a 1 based index, how would you interpret the 0? Currently program panics at Argument interpretation phase.

  • I know its user produced content. But there are still rules that are enforced by Archteam and they host and link to it. And why not tell people about security issues? They could at least tell people in the news, so we can act accordingly. This is super disappointing. Is there any trustworthy RSS feed that covers this?

  • There are couple of factors that makes this a confusing topic.

    Vim: On a high level, normally Vim (and Neovim) have their own clipboard system. Vim has multiple internal clipboards that can be used like variables and accessed with other commands. So its kind of sandboxed from your system. But you can explicitly use the commands to access the system clipboard. There is a configuration you can set to use the system clipboard by default.

    Linux: Unlike Windows, in Linux we also have two kind of clipboards: the "system" clipboard as you know and the "primary" clipboard. This has nothing to do with Vim and is a feature on Linux systems itself. If you in example in your browser mark a text without copying, it is automatically copied into the "primary" clipboard. Then you should be able to access and paste it with middle mouse button in example. The system clipboard where you explicitly copy stuff is not affected by it.

    You should read following documentation: 09.3 The clipboard - Neovim

  • Its sad we need to emulate

    "WINE" stands for "WINE Is Not an Emulator". I personally think (no confirmation) that in the past it stand for "WINdows Emulator", and after lot of discussion they might have changed it. Peace out.

  • I'm so drunken from lot of WINE news recently. Not complaining though.

  • Perverts!

  • This is a really good introduction.