A "don't do wrong broken shit" checkbox in Visual Studio? You wish.
-
Yes. These are all wonderful points.
-
yy p :w :qYeah, you can do some cool shit when you learn it. But damn is it counter-intuitive!
-
These are all wonderful points.
Wonderfully irrelevant.
The fact that programs X, Y, Z are broken is completely separate from the fact that Visual Studio is broken.
-
The fact that programs X, Y, Z are broken is completely separate from the fact that Visual Studio is broken.
Yeah, but since we all pretty much agree with that, we now need to find a new topic to fight about.
-
Oh I see. Well carry on then.
-
There is no application (other than Visual Studio) in which Cut will do anything with no selection. Ditto that with Copy.
Well mine wasn't irrelevant or wonderful really. I was just responding to this.
-
Actually, the folklore is that Microsoft stole it from Apple, when they wrote Excel for Mac OS and then ported it to Windows.
Then why is the entirety of Excel's Clipboard support still so hideously and fundamentally broken?[1]
(Along with much of the Excel UI. They always seem to be two to three versions behind the rest of the Office suite. MDI is so last-decade.)
[1] I know the reason given by MS employees, which was so stupid and fundamentally wrong that I wonder what the real one is.
-
The fact that programs X, Y, Z
are brokenhave features I don't like is completely separate from the fact that Visual Studiois brokenhas a feature I don't like.
FTFY
-
As the saying goes, every feature you can't turn off is a bug.
-
I have no idea what that means
It is an on－screen keyboard. It is very useful in Japanese where it has handwriting recognition and lists of letters. It is mapped to F5 by Microsoft IME and overwrites the feature of browsers refreshing even.
http://1art.jp/word/word2007/chapter9/img/img18.GIF
-
Oh dear. That means you didn't get my joke.
ETA: Here is the stock Windows 8 OSK.
-
Oh dear. That means you didn't get my joke.
I feel obligated to point out that the post I'm quoting was, IMNSHO, quite pedantic. He literally missed (out on) my joke because he didn't know what an OSK was. I'm sure he'll be laughing when he reads it.
-
let's complain more about things working exactly as they are supposed to.
-
But nano uses
^Kand^U, not established cut/paste keys.
-
I know 😜
-
You mean, you were just being a thorn in blakey's side?
TBH, I never stumbled about the Ctrl+XCV issue in Visual Studio so far. It doesn't seem like something I'd ever intentionally use, though.
-
Well, a quill, but yeah 😋
-
And then there's Linux where just selecting something sticks it into an additional clipboard you can paste from using middle click (I buttume there's a keyboard shortcut too but I never looked for it).
It's awesome feature when working with terminals. It's the most annoying thing ever in a web browser (by middle-clicking on a page I totally meant to go away and google forgrep -ril "some stuff" ~/.config...). Especially annoying on laptop, where two-finger scroll sometimes gets interpreted as two-finger click.
-
Sometimes I wish for an option to make Shift+Insert work slightly differently from Ctrl+V, placing the caret at the beginning of the pasted text instead of the end.
That's where the caret was placed in an old DOS editor that only supported the "old" shortcuts.
-
I don't see why sending signal 2 would copy text...
I don’t see why sending \x03 would send signal 2...
-
I have no idea what that means, but all I can think of is, "OshKosh, b'gosh!"
"Oh look, it's an on-Screen Keyboard!"There is no application (other than Visual Studio) that I know of or admit to exist in which Cut will do anything with no selection. Ditto that with Copy.
FTFY.But you're right
-
-
It was Xerox, for the SmallTalk environment
Possible, but I suspect not [still searching the history books. The first public release of SmallTalk was in 1980, at least 5 years after I had seen ctrl-c ctrl-v in other application. Now the original (very private) ST build was in 1972, so it is possible this was the point of origin, but then one needs to figure out how in leaked into at least one other product prior to June 1976.Much more likely is an origin within the CP/M ecosystem [Digital Research / Gary Kildall] as the time frame is right, the project was publically available, and the paradigm existed in MANY of the programs..
-
-
I feel obligated to point out that the post I'm quoting was, IMNSHO, quite pedantic. He literally missed (out on) my joke because he didn't know what an OSK was. I'm sure he'll be laughing when he reads it.
I freely admit (as I already did) that I didn't know WTF an OSK was. But I'll also admit that you got a little chuckle out of me.
-
let's complain more about parts of things working exactly as they are supposed to.
Forum software? There's a thread about that somewhere round here... :rummage:
-
I don’t see why sending \x03 would send signal 2
In case you weren't trolling, ^C sends SIGINT which is usually #defined to be 2.
-
Ok if you read this, you agree to never tell me I don't criticize Microsoft products. Agreed?
No, I don't agree.
But just yesterday you said that .NET 1.0 was a tech preview, so I guess you are starting to see the light
-
But just yesterday you said that .NET 1.0 was a tech preview, so I guess you are starting to see the light
Actually, didn't he stop talking about it once he was--again--proved wrong?
-
Actually, didn't he stop talking about it once he was--again--proved wrong?
No, he did not ;)
-
-
TBH, I never stumbled about the Ctrl+XCV issue in Visual Studio so far. It doesn't seem like something I'd ever intentionally use, though.
The usual way I stumble is when I'm trying to quickly (too quickly, not watching) copy/paste a variable name between programs. dbl-click, ctrl+c, alt-tab, ctrl+v. Dammit.
-
In case you weren't trolling
I was.^C sends SIGINT
Not always. Pressing ^C makes the terminal send the ASCII character \x03. The kernel’s TTY layer may end up sending a SIGINT upon receive of a \x03, but it depends on the current TTY mode.
-
Fortunately, Microsoft provides a "don't do wrong broken shit" checkbox in its settings:
They also provide a checkbox which is supposed to disable that stupid warning message that makes me angry whenever I open a project located on a network drive. Except that checkbox doesn't do anything (useful) either.
-
Could be worse. Could be Code Warrior, which even manages to have broken #ifdef highlighting that only ever shows one project configuration, regardless of which one is active.
And yes, I have ticked the "Yes, I do want the highlighting to follow the build config because anything else is belgiuming stupid."
Which is not the default.Not keen on Eclipse to start with but this is even more broken.
-
There are other applications that cut & copy without a selection. See: every image editor.
Hmm...looking at what I have installed, cut and copy without a selection:- Photoshop CS6: Do nothing.
- Illustrator CS6: Do nothing.
- Paint.net 4: Do nothing.
- Paint Shop Pro 8: Operate on the current layer.
- Paint (Windows 7): Do nothing.
- GIMP 2: Operate on the current layer. (Shows a pseudo-selection around the image.)
It'd be nice if you could disable it in Windows apps that have a "cut/copy without a selection" feature, but it's not a big deal to me. (At the point where they get this fancy about selections, applications also tend to support multiple undo.)
-
I had someone say, "You know, I like [one minor feature] of [medium-large Minecraft mod], how can I get just that?"
So I told them, "Go to the config file and turn everything else off". And it worked, because the code has stuff like
if (obj.getFeature().isEnabled())in critical places in the loading code, which resulted in the on-update handlers etc not being called, and therefore not breaking!
-
Just like how when you assign a null string to a variable, it doesn't change but keeps its previous value, right?
Are we talking about PHP again?
-
I had someone say, "You know, I like [one minor feature] of [medium-large Minecraft mod], how can I get just that?"
So I told them, "Go to the config file and turn everything else off". And it worked, because the code has stuff like if (obj.getFeature().isEnabled()) in critical places in the loading code, which resulted in the on-update handlers etc not being called, and therefore not breaking!
That's probably the most irrelevant post this whole month.
-
-
That's probably the most irrelevant post this whole month.
There's some pretty stiff competition though, Shirley?
-
I was replying to the statement that "every feature you can't turn off is a bug" with an anecode of that taken to the extreme.
.... Nope, wasn't relevant, you're right.
-
At work, I have to save anything remotely important on the network drive, since that’s backed up daily (the client PCs are not). Maybe that’s the real WTF, but I still should be able to teach Visual Studio to trust the files on my network drive.
-
There are two kinds of bugs:
- something that is clearly wrong, that cannot be defended by any arguments (e.g. crashes, wrong calculations, graphics glitches, Qt's weird behavior when scrolling on Linux)
- something that is a feature you don't like
If you can turn off the second kind of thing, it's not a bug. If you can turn off the first kind of thing, it's still a bug.
inb4 spacebar-heating
-
At work, I have to save anything remotely important on the network drive, since that’s backed up daily (the client PCs are not).
Sounds like someone isn't using version control. Or has developed regulations that ignore the fact version control exists.
-
-
Sounds like someone isn't using version control.
Maybe they copy the repository onto the network server every night, so it's backed up properly?
-
How did you jump to that conclusion?
By the fact you have to backup your working directory.
-
By the fact you have to backup your
working directorycopy of the repository.FTFY (We’re using Git.)
Also: What’s so hard to understand about that? Sometimes, it takes me up to 5 days to finish a new feature and push my changes to the central repository. And I don’t want to risk losing 4 days of work in case my HDD fails (again).
-
FTFY (We’re using Git.)
Branches anyone?Also: What’s so hard to understand about that? Sometimes, it takes me up to 5 days to finish a new feature and push my changes to the central repository. And I don’t want to risk losing 4 days of work in case my HDD fails (again).
And you totally cannot commit before you finish, especially since you're using the best tool on the market when it comes to branching and merging that also has squash feature.
