![]() There are other applications of this as well I can think of parsing data for xml based databases that have incompatible strings or blocks, or even some old flash-based games that use XML for the adventurer file instead of Binary hexadecimal strings. There was a lot of code to go through, and thankfully I’m OCD enough to mark all of my edit decisions in basic markers, which allowed me to redo whatever I needed to in CS6, then move straight into Encore for a DVD. I got a 2020 file to open up in 2013, and then from there saved again, did this again and got it to open in CS6. If, like me, you are editing some XML files from premiere pro or similar to get the versioning to match and drop a few non-compatible pieces for an older version, you can search whole xml blocks with only the main descriptors and none of the actual values needed. I can also confirm that you can do this, and then add another. * at the end of the word selects the line and new line marker. ![]() Reply to this email directly, view it on GitHub, or mute the thread.I can confirm that putting \r\n into the find box after the second. You are receiving this because you commented. Sometimes I want to take pieces out and move them somewhere else, but if VSCode pasted into the lines following my cursor, instead of making a new line for each one that I had, I would have a huge mess of code.If I'm understanding the suggestion, in order to make that work, I would have to enter in a bunch of blank lines (and I would have to know exactly how many before being able to paste) in order to make sure that part of my column selection doesn't end up getting pasted inside another line which already has code? That seems like a pretty big hassle to me. Subject: Re: Column selection ( that functionality could be problematic for some of the copy/pasting I do with column selection. Notepad handles this perfectly.Usually I'm not a fan of copy-cats but this is no time to be original with something that is already proven to work perfectly haha. Seems to be the same as sublime, basing it on the number of cursors you have when pasting vs the number of lines you have copied.each N line is pasted once, at each cursor corresponding to its line numberĪs far as I can tell (from the perspective of an end-user, anyways), sublime doesn't appear to distinguish between items copied from multiple cursors or single cursors stretched across multiple lines.all N lines are pasted M times, following the functionality of pasting with 1 cursor.all lines are pasted as is, including new lines, pushing text after the cursor down.To add some potentially relevant information, here's how a couple other editors appear to handle it: I think I would have pressed ctrl left arrow to move all the cursors in the gif example, then pasted them from the moved multi-cursors, but I can see how being able to click one position would potentially be useful. I was unsure of exactly how visual studio handles it, so thank you for the insight. I agree that it feels a bit naive, but you're probably right that it's what the user intends in most cases. Items cannot be moved if the cliptext library is sorted. Move cliptext item Drag and drop the cliptext item to the desired position in the list box. This command presents Edit cliptext Item dialog box. Then choose Edit command at the popup menu. Thanks for asking that seems like a fair distinction to me. Click right mouse button on the list box. ![]() If I could only have one I would much prefer the expected classic behavior,Īs in VS, as that permits me to select the vertical data what I want/chooseĪnd not be forced to include more data CR¹s in my selection.Ĭan we have the classic behavior as implemented in VS? Then maybe your current VSCode way with aĪlt Shift and mouse movement, as a secondary option. In a perfect world the classic VS way would be the default, implemented with It is a variable length selection at each line. The current VSCode implementation is not a vertical selection box behavior. Not always extended out to the CR at a variable horizontal distance. An expected vertical selection would be my desired box of data, The problem with the current VSCode behavior is that it specifies in theĭesign that the "box" selection will always be to an "end of line" condition, including Your second demo as VSCode performs on master is interesting and of value but "correct" way, in that it is the classic way we expect that action to The way VS performs a vertical selection is the
0 Comments
Leave a Reply. |