Sensible default save location



  • @superjer said:

    I did read it. This particular task has come up once for me, and never for you. Which doesn't change anything because my point is Vim is great at solving tedious editing tasks. Like any of them.

    The months it took you to learn its arcane UI are not worth the minutes you save a year using it.

    @superjer said:

    Personally, I'm not a fan of frequently reaching for the mouse to try to precisely click on tiny characters.

    So turn up the font size.

    @superjer said:

    In Vim I can just say "go to the next x character", "select the text inside the quotes" or "let's change the conditional" and my favorite, "do it again".

    Except perhaps the latter, almost every editor lets you do tasks like that. The only difference is you haven't learned any other editor, you learned Vim. And since you're head's swimming in Sunk Cost Fallacy, now you have to come here and preach about how great it is.


  • BINNED

    @blakeyrat said:

    @Cassidy said:
    Sideways Q: when did VS had regex support?

    Always? Or at least, as long as I've used it.

    VS6 definitely didn't have it.



  • @blakeyrat said:

    The months it took you to learn its arcane UI are not worth the minutes you save a year using it.

    You overestimate and underestimate, respectively. And even if it didn't save me ANY time, I just enjoy using it more than other editors.

    @blakeyrat said:

    So turn up the font size.

    And see less? It lessens the problem, but doesn't get rid of it.

    @blakeyrat said:

    @superjer said:
    In Vim I can just say "go to the next x character", "select the text inside the quotes" or "let's change the conditional" and my favorite, "do it again".

    Except perhaps the latter, almost every editor lets you do tasks like that.

    I believe you. But what are the commands to do those and do you actually use them? Also, without "do it again" they all lose a lot of value.

    @superjer said:

    The only difference is you haven't learned any other editor, you learned Vim.

    Vim is only the most recent editor I've learned. I didn't know any of the other ones (Notepad++, gedit, VS, etc.) had such commands. Maybe they aren't discoverable enough? What are they again?

    @superjer said:

    And since you're head's swimming in Sunk Cost Fallacy, now you have to come here and preach about how great it is.

    How much time is appropriate for leaning a tool I use 40 hours a week? And how are you so sure it took me 10, 100, 1000(?) hours to learn Vim? 



  • Notepad++ is extremely discoverable. It has a nifty little Plugins menu where you can click and see at a glance a list of everything it can do. And if it can't do something, there's a 103% chance that a plugin exists to do it, you just have to download and install it. It also has macro recording which I've never ever had to use, but if I needed it I shouldn't have too much difficulty figuring out the five options in the Macro menu.



  • @mott555 said:

    Notepad++ is extremely discoverable. It has a nifty little Plugins menu where you can click and see at a glance a list of everything it can do. And if it can't do something, there's a 103% chance that a plugin exists to do it, you just have to download and install it. It also has macro recording which I've never ever had to use, but if I needed it I shouldn't have too much difficulty figuring out the five options in the Macro menu.

    Several of my friends use Notepad++ on my recommendation. It's not for me, but they seem to love it. I don't think it has a vi emulation plugin, but a lot of editors do, like VS for instance.

    But it's messy to turn a non-modal editor into a modal one (if even possible), and they only support a tiny fraction of the functionality of real Vim. You can turn Vim into a non-modal editor as well (:set insertmode), but it has the same kinds problems.

     



  • @superjer said:

    But it's messy to turn a non-modal editor into a modal one (if even possible), and they only support a tiny fraction of the functionality of real Vim. You can turn Vim into a non-modal editor as well (:set insertmode), but it has the same kinds problems.

    I don't even know what this means.



  • @mott555 said:

    @superjer said:

    But it's messy to turn a non-modal editor into a modal one (if even possible), and they only support a tiny fraction of the functionality of real Vim. You can turn Vim into a non-modal editor as well (:set insertmode), but it has the same kinds problems.

    I don't even know what this means.

     

     

    What makes Vim modal:

    http://en.wikipedia.org/wiki/Vi#Interface

    Or as a general concept in computer interfaces:


  • Discourse touched me in a no-no place

    @mott555 said:

    there's a 103% chance
    Stop talking bollocks.



    Please.



    In this context, any number above 100 is meaningless.



  • @PJH said:

    @mott555 said:
    there's a 103% chance
    Stop talking bollocks.



    Please.



    In this context, any number above 100 is meaningless.
    He obviously meant 103 (mod 100), which is 3%.



  • @Zemm said:

    In TextWrangler it's ⌘-double-click. And ⌘G to search again. (Or select, ⌘C, ⌘F, ⌘V, enter for the initial search.

    ⌘E takes your current selection and uses it as the search term without opening the Search dialog in just about all OS X apps. Hit ⌘G to actually search (not ⌘F — that opens the Search dialog), repeating as necessary; ⇧⌘G searches backward.

    @Zemm said:

    And the ⌘G vs ⌘K inconsistency between programs annoy me too.

    ⌘K is not a standard key binding for anything related to searching in OS X, to the best of my knowledge. Ctrl+K is kill, though, like in Bash :)

    @Zemm said:

    IAnd F3 doesn't work on many (any?) Mac programs.

    That's because ⌘G has the same functionality as F3 has under Windows.



  • @ender said:

    2005 is the oldest one I have installed, and it has it.
     

    Aha, okay - quite some time, then. I recall someone telling me about VB and regex support in early 2000s.

    @blakeyrat said:

    Hasn't reading this forum taught you that people are fucking idiots?
     

    I didn't read a forum to teach me that lesson.

    @blakeyrat said:

    Why are you trusting a fucking idiot to tell you what features a product has? Look for yourself.

    I just thought asking someone that uses said product and could provide an answer was much quicker than finding somewhere with a windows image, installing VS onto it then examining those features. Perhaps your experience differs, but it was a shorter route for me.



  • @Ben L. said:

    @PJH said:
    @mott555 said:
    there's a 103% chance
    Stop talking bollocks.

    In this context, any number above 100 is meaningless.
    He obviously meant 103 (mod 100), which is 3%.
     

    Maybe he meant a nonexistent chance?



  • @Gurth said:

    ⌘E takes your current selection and uses it as the search term without opening the Search dialog in just about all OS X apps.
     

    Thank-you. I like learning new keyboard shortcuts. I never saw that menu option.

    @Gurth said:

    ⌘K is not a standard key binding for anything related to searching in OS X

    Unfortunately there's things called cross-platform programs which don't always use the OS X bindings. Eclipse uses ⌘K for "Find Again". ⌘K in Firefox is "Web search" which just puts the cursor in the Google search box. Adobe Flash CS5 apparrently uses F3 for "Find Next" but it seems to bring up the global "Find & Replace" dialog, not the one local to the AS editor.

    @Gurth said:

    Ctrl+K is kill, though, like in Bash :)

    Don't you mean ^C? ^K clears from the cursor to the end of the line in bash, which I just tested in TextWrangler does the same (actually "cut" to clipboard); I use ^A and ^E a bit since the Mac Home/End keys are document-based instead of line-based. But then in vim I could use D (or d$), ^ and $ respectively.

    @blakeyrat said:

    The reason Vim has a high learning curve isn't because it has more features, or advanced features, or more advanced features. It's because its developers don't give a shit about the quality of the product they are developing.
     

    I always thought it was more to do with technical limitations of computers in the 1970s/80s. Even though it still failed: my first experience with vi was on a Digital Unix workstation which lacked an Esc key (and you know how much vi loves you pressing Esc!) Originally they got us to press F10 and deal with the beep from invalid command, but I figured out ^[ produced an Esc without the beep! From memory it didn't have cursor keys either, so vi's h, j, k, l were useful.


Log in to reply