Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it.
I wish getting out of the find text box was simpler and more intuitive.
Maybe it's just me.
CotEditor – Text Editor for OS X
71–80 of 198 posts
Re: CotEditor – Text Editor for OS X
#72Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it. I wish getting out of the find text box was simpler and more intuitive. Maybe it's just me.
Not just you. Sublime's find is anything but.
Re: CotEditor – Text Editor for OS X
#73Re: CotEditor – Text Editor for OS X
#74Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it. I wish getting out of the find text box was simpler and more intuitive. Maybe it's just me.
I don't know how it could be easier: You position inside a word anywhere, press CMD+OPTION+G; the next word is already selected, you can already edit it, no need to bring up Find panel.
Re: CotEditor – Text Editor for OS X
#75Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it. I wish getting out of the find text box was simpler and more intuitive. Maybe it's just me.
cmd + e will mark the current selection (or current word if there's no selection), cmd + g (or cmd + shift + g to go backwards) will find other instances of it. ctrl + cmd + g will find all instances of the current word, which you can edit simultaneously.
Re: CotEditor – Text Editor for OS X
#76Earlier quoted context omitted.
Atom is strange to me, it seems like a less familiar Sublime Text with no real distinguishing features.
The distinguishing feature is it's horribly slow with large files. The performance is an order of magnitude slower than sublime text. And it doesn't auto-save unsaved work if it closes. Both deal breakers for me.
Extremely slow to load, too. Brackets and TextMate load much faster.
Re: CotEditor – Text Editor for OS X
#77Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it. I wish getting out of the find text box was simpler and more intuitive. Maybe it's just me.
For that use-case, isn't control-d / cmd-d pretty quick?
Re: CotEditor – Text Editor for OS X
#78Earlier quoted context omitted.
Why do you have text files that are 200MB? Why don't you separate that into multiple files? 200MB of text? Moby Dick is 1MB in plain text. The Holy Bible is like 4MB in plain text. What is in your files? I think you may be doing something wrong.
We deal with data sets that are several GB in size, and so I'm already using just a subset of the data. These files are loaded by programs into memory and serve customers via a REST API, and it's not uncommon that we have to manually inspect or change the files from time to time. Our use of large text files isn't only internal; our software also processes delimited text files for customers, and these can run into the…
Any particular reason you're not using a database?
Re: CotEditor – Text Editor for OS X
#79Why is 'find' so horribly difficult to use in sublime? I want to find another instance of the current word and then quickly modify it. I wish getting out of the find text box was simpler and more intuitive. Maybe it's just me.
I don't know how it could be easier: You position inside a word anywhere, press CMD+OPTION+G; the next word is already selected, you can already edit it, no need to bring up Find panel.
Or double-tap Command+D.
Re: CotEditor – Text Editor for OS X
#80I'm pretty effective with vim, so much that other 'normal' editors like sublime & other modern gui editors make me feel a little crippled. That is a problem, because you need to be flexible about things in life. Has anyone succeeded in deliberately changing editors, even when not feeling like it's necessary? I'm especially curious how I could start using emacs, and actually get up to speed with it instead of using it…
I moved between being a life-long vi/vim'er to Sublime and more recently Atom.
I only use Atom for coding and vim for just about everything else.
The most difficult part for me is that i'll open a file in vim and then consciously go "no" and fire it up in one of the other editors.
Why? because I like to keep my vim more clean. I've seen some of the really complex vim configs out there and they just didn't "do it" for me.
So if i want complex things like syntax highlighting I go with Atom.