[deleted]
You can't do that because I hate you
151–160 of 216 posts
Re: You can't do that because I hate you
#152What a bad article!
He wants a function to work as a keyword!
He wants comments word wrapped by default, when this would break comments that contain stuff like packet fields schemes.
Terrible ideas, and he complains they aren't the default. Well that's because they aren't good ideas and he hasn't thought about it long enough to figure it out.
Re: You can't do that because I hate you
#153[deleted]
Re: You can't do that because I hate you
#154Haha, made me laugh out loud at how true this statement feels, even though it is probably not true:
"If you don't enjoy programming, don't worry, it is not your fault. Thousands of people around the world work hard day and night to make programming as miserable for you as possible."
Re: You can't do that because I hate you
#155> But it does neither. It acknowledges your intent and refuses it. It’s saying “I know exactly what you want to do, but you’re doing it wrong. Do it right next time.” Programming languages follow rules and programmers should follow the rules. Just because mistake is common doesn’t mean the language should incorporate it into its functioning. That makes inconsistent behavior and is a pain in the long run because inste…
I think it's quite reminiscent of car infrastructure, in that you can know all the rules, but primarily you're interacting with other people who have varying knowledge and skill with the rules. The dutch make a strong case for the rules to follow what the people do naturally, and using design to make the correct thing the easiest one, rather than presenting a stiff ruleset and expecting people to contort themselves a…
From the Zen of Python:
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Re: You can't do that because I hate you
#156I have a similar pet peeve in software, what I refer to as ‘Don’t Suck’ Buttons. A ‘Don’t Suck’ Button is a setting, turned off by default and usually hidden in a corner of the UI or configuration file, which fixes a common issue that new users experience, and/or turns on the behavior that everyone wants from the product in the first place. The best examples of ‘Don’t Suck’ Buttons involve settings with no obvious di…
[deleted]
Re: You can't do that because I hate you
#157This is literally Typescript vibes all around... Awful dev experience, it's a fucking joke and people seem to like it...
Re: You can't do that because I hate you
#158Earlier quoted context omitted.
Do you have a list of favorites?
On Mac, assign traditional keybinds to Command/⌘ shortcuts (⌘-C/V for copy-paste, -S for save, etc). Display the current column number in the modeline with (setq column-number-mode t) Delete the selected area when overwriting by enabling (setq delete-selection-mode t) Save sessions (all open buffers/files) automatically on quit with (setq desktop-save-mode t) Display line numbers in the left gutter with (setq global-…
I agree that you need to customize Emacs rather heavily before it can be used as a "modern" editor.
I'm not a fan of most of your changes though, which highlights how hard it is to have defaults that please everybody in something as complex as Emacs.
Re: You can't do that because I hate you
#159Earlier quoted context omitted.
Right, it's nothing to do with it being "newly added". That issue had been filed by its OP as a feature request. It then got repurposed into a tracking issue for the feature, but it's not following the standard tracking issue template that lists any blockers, stabilization steps, etc. (Compare to https://github.com/rust-lang/rust/issues/119364 that happens to be the newest "Tracking issue" atm.) Also since the OP did…
> Right, it's nothing to do with it being "newly added". It absolutely was, but now it seems to be mostly that the stabilization process is tedious enough that nobody has done it yet for this tiny utility function. There are tens of other tiny utility functions in the same situation that have been sitting for years, I run into them all the time. The whole situation surrounding "unstable features" is just super disapp…
>It absolutely was
No, there is no such absolute requirement that "newly added" functions cannot be stabilized. Off the top of my head: https://github.com/rust-lang/rust/issues/111544 `OsStr::as_encoded_bytes` was proposed in 2023-05, finished being implemented in 2023-07, stabilized in 2023-09, and released in 2023-11.
>https://news.ycombinator.com/item?id=38801228
The reason attr of "newly added" is the reason to *mark the function unstable* when it was implemented. It's not the reason to *prevent it from being stabilized.*
Re: You can't do that because I hate you
#160Earlier quoted context omitted.
Do you have a list of favorites?
On Mac, assign traditional keybinds to Command/⌘ shortcuts (⌘-C/V for copy-paste, -S for save, etc). Display the current column number in the modeline with (setq column-number-mode t) Delete the selected area when overwriting by enabling (setq delete-selection-mode t) Save sessions (all open buffers/files) automatically on quit with (setq desktop-save-mode t) Display line numbers in the left gutter with (setq global-…
the desktop-save-mode option is gold... thanks