|
kdmote wrote: just Ctrl-Shift-V a couple times and VS will cycle back through your recent clipboard items.
Huh, no I didn't know that!
Caveman Marc
|
|
|
|
|
Interesting way to clear the clipboard so as to not have 'forgotten' items in there that may be inadvertently posted later.
|
|
|
|
|
Tim Carmichael wrote: way to clear the clipboard so I've done that when I've copied and pasted large amounts of information from other projects or applications just to clear the clipboard.
It was broke, so I fixed it.
|
|
|
|
|
What ever happened to the multi-chased copy paste?
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
It was too multi-chaste, and died out since it didn't copy...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Hold still. Bubba the angry male sheep wants to hurt you now.
Software Zen: delete this;
|
|
|
|
|
I wish they would separate that option to one for copy and one for cut. Because I agree that copying a blank line is just silly. Cutting however?
When I'm rearranging code (commenting / moving similar methods/props next to each other, etc..., ergo, a lot of cutting/pasting), I use ctrl-x to cut (read: delete) blank lines all the time. Much easier to do with one hand on the mouse, and the other on ctrl-x. ctrl-delete requires me to leave the mouse or contort.
|
|
|
|
|
And I was just about to enable that option... good catch.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Why won't you just press delete ?
|
|
|
|
|
Because some(many) times the "blank" lines have extra spaces or tabs in them. Delete will only get rid of one of the characters. ctrl-x eliminates the whole line. And I think these faux-blank lines still count as blank as far as this option is concerned.
Also: since this is usually in the midst of moving code, my hand is already over the ctrl-x keys.
|
|
|
|
|
In VS I prefer to use [Ctrl]+[Shift]+[L] to remove empty lines. That way I don't lose what's in the clipboard. It normally happens when I decide to move chunks of code around by cutting what I want to keep, removing all lines to clean up, then going to the new location and pasting. That way I don't have to scroll around or remember where to clean up again.
My plan is to live forever ... so far so good
|
|
|
|
|
If you think about the vast number of options in VS (in Tools => options), and wonder why and WTF a lot of them do, then ya, it makes you think "Why MS, why?"
But what really bugs the piss outta me is when menu & shortcut options change from one version of VS to another.
If it's not broken, fix it until it is
|
|
|
|
|
That is the second setting I change when installing a new copy of any version of VS.
My plan is to live forever ... so far so good
|
|
|
|
|
Did you ever try Ctrl+Shift+V after that? Twice
Banking establishments are more dangerous than standing armies. T.Jefferson
|
|
|
|
|
Nope, never heard of that one!
There are times, Microsoft...and inventing a cure for a problem you cause without actually curing the problem...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It really does wonders to paste what you intended originally. I never heard about this combination myself until my colleague has told me about it when I was grumbling pretty much like you about empty line copied to clipboard instead of pasting
Banking establishments are more dangerous than standing armies. T.Jefferson
|
|
|
|
|
Why? Retentive code reviews.
|
|
|
|
|
I know well the annoyance when I too miss the "v" key and press the "c" key instead. Indeed, WTF were they thinking!?!
I started using BRIEF (Basic Reconfigurable Interactive Editing Facility) in the late 80's and it's keyboard shortcuts have stuck with me ever since.
Cut-Copy-Paste are such fundamental operations they demand a single key all their own; none of this rubbish multi-finger pinky-x, pinky-c, and pink-v!
Insert ==> Edit|Paste <br />
Keypad + ==> Edit|Copy <br />
Keypad - ==> Edit|Cut
Simple, intuitive, and since I do far more copying than cutting, they used the enlarged "+" key on the numeric keypad to give your finger an ample target.
Brief was (is) a brilliant editor and it's ideas have stood the test of time IMNSHO.
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
|
|
|
|
|
And it had multiple source "windows", and mouse support, and...
I loved it to death - for the first time, you could look at several parts of your code at the same time (Microsoft, are you listening?)
I think I still have the original disks and manual in the spare room - but they'll be on 360K floppies (possibly 720, I can't remember) and I don't have anything to read them any more!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: (Microsoft, are you listening?)
No
My plan is to live forever ... so far so good
|
|
|
|
|
http://www.briefeditor.com/download.htm[^]
Free.
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
|
|
|
|
|
Get thee behind me, Satan!
I've got too used to Intellisense, and I'm trying not to install too much old stuff - I still have QuickC for DOS installed, and had to force myself not to install Ami Pro '97 on this PC (because it was a much, much better work processor than Word is, even now...)
Nooooo.....I won't do it....I won't....I'll just download it in case I need it later, honest....
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I loved B.R.I.E.F. It was made my Underware Software (seriously).
The thing I really miss about the old editors was that they could edit HUGE files that would not fit into all available memory. I needed that just yesterday! Notepad refused to load a 1.9gig text file on a 64bit OS with 4gigs of free memory!
BRIEF had a great macro language as well. I wrote a macro to provide popup context menus for the different C structs <-> DB mappings we used on a series of projects. It was like intellisense 0.1. Somewhere along the way, they converted the macro language from a LISP-like prefix syntax to more of a C syntax.
Then the IDEs started coming out and eclipsed* the single purpose editors...
*bad pun
|
|
|
|
|
TextPad ...
|
|
|
|
|
TextPad failed on a 15Gig file with 5.9Gigs of available memory.
It was worth a try! Thanks for the suggestion.
"The file size exceeds the limit allowed and cannot be saved."
I don't really need an editor for these large files, just a viewer!
I found some other suggestions I will try.
|
|
|
|