News for hackers. Stuff that matters.
Re:Visual Studio Code 1.0 by enjoy-your-stay on Thursday April 14, 2016 @04:12PM (#11499968)
Just wanted to say I find Notepad++ to be an excellent tabbed editor, especially for XML or SQL. I use it on windows all the time and really miss it on OS X where I find Textmate to be a bit awkward.
Re:Visual Studio Code 1.0 by jongalloway2 on Thursday April 14, 2016 @05:18PM (#11500426)
I've been a long-time fan of Notepad++, but it's a text editor. You can extend it to make it work better with specific programming languages (e.g. here's a post I wrote 10 years ago about adding language support http://weblogs.asp.net/jongalloway/creating-a-user-defined-l...) but it's fundamentally a text editor.

VS Code is a code editor. It has IntelliSense (not text-matched autocomplete, IntelliSense), debugging support, git integration, parameter hints, go to definition, code peek, etc. (http://code.visualstudio.com/docs/editor/editingevolved). The goal is to give you code editing features with the speed and simplicity of a text editor.

They're both free and lightweight, so I use them both pretty much daily.

Re:Visual Studio Code 1.0 by kevin_thibedeau on Thursday April 14, 2016 @07:56PM (#11501155)
Notepad++ is very useful but I wish some features would be updated. The dialogs are awkward to use at times. The XML for defining custom syntax highlighting is atrocious. It's like they took a pre-XML config file and shotgunned tags into it without planning a rational format. Keywords are specified using long strings delimited by CR/LF entities for no good reason other than to destroy readability. It would be nice if an more modern hightlighting engine could be inserted as an alternative to the clunky ad-hoc design it currently has.
Re:Visual Studio Code 1.0 by jsingleton on Friday April 15, 2016 @05:32AM (#11503122)
As you say, both are useful for different things. They complement each other if you use the right tool for the right job.

I find Notepad++ is great for handling really large files and changing UTF encoding or line endings. VS is good for pretty print formatting code/XML to be more readable, among many other non-text things such as debugging.

Re:Visual Studio Code 1.0 by coldtea on Friday April 15, 2016 @07:26AM (#11503463)
>and changing UTF encoding or line endings

If you need to do those things often, there are specialized tools, including in the command line, and for batch processing.

No need to do it in an editor.

Re:Visual Studio Code 1.0 by jsingleton on Friday April 15, 2016 @08:00AM (#11503598)
I don't need to do this often but occasionally you'll need to fix inconsistent line endings, change encoding to UTF-8 or remove a BOM [0] (to stop  being prefixed by some old software).

[0] https://en.wikipedia.org/wiki/Byte_order_mark

Re:Visual Studio Code 1.0 by coldtea on Friday April 15, 2016 @12:19PM (#11505481)
Yeah, I know, had to do it some time or another.

In OS X and Linux (and Windows with Cygwin etc) there are several command line programs such as unix2dos (line ending conversion), iconv (encoding conversions) etc for doing just that, so that you don't need to do it in an editor and can even automate the work.

Re:Visual Studio Code 1.0 by klodolph on Thursday April 14, 2016 @05:34PM (#11500523)
Coming from OS X, there are a bunch of minor things missing in Notepad++ that I'm used to having on OS X. Like the ability to drag tabs between windows with the mouse, to move new tabs to a new window, or to create a new file and immediately save it. The scrolling in Notepad++ is also a little buggy. Just to give you a perspective about what the other side thinks, since you inevitably develop different habits in different editors, and those habits break when you switch.

That said, I use too many editors for my own good. (I'm active in both main churches.) Neither Notepad++ nor TextMate are competitive with VS Code, Emacs, or Vim, IMO, and I use all five regularly.

Re:Visual Studio Code 1.0 by Razengan on Thursday April 14, 2016 @10:36PM (#11501701)
> Coming from OS X

Also, do Windows editors have that Alt+drag rectangular text selection feature that most/some OS X apps have?

Re:Visual Studio Code 1.0 by reitanqild on Friday April 15, 2016 @01:27AM (#11502388)
No, it is implemented by each editor/ ide independently with their own modifier.

On the contrary we have mostly consistent ctrl/shift + arrow behaviour over the last 15 or more years(I don't know before that). :-)

Re:Visual Studio Code 1.0 by Razengan on Friday April 15, 2016 @02:26AM (#11502574)
> On the contrary we have mostly consistent ctrl/shift + arrow behavior

Are you saying Windows has consistent Control/Shift + arrow behavior?

OS X is pretty consistent about this too, though Control+Arrow moves between Desktop Spaces, not related to text, but you can modify a lot of system/app shortcuts from Preferences -> Keyboard -> Shortcuts.

Re:Visual Studio Code 1.0 by reitanqild on Friday April 15, 2016 @02:37AM (#11502611)
When I had a Mac (2009 - 2012) what modifier to use for different text movement operations varied wildly, even between the built in applications.

Mac using colleagues explained that it was because the applications where written using different toolkits.

Re:Visual Studio Code 1.0 by eric-hu on Friday April 15, 2016 @09:55AM (#11504285)
Ctrl arrow in Windows jumps by word. In os x, it's option arrow. I believe it's widespread but not global.
Re:Visual Studio Code 1.0 by reitanqild on Friday April 15, 2016 @01:08PM (#11505913)
I know.

Problem is: until at least 2012 not even Apple was consistent about it.

Re:Visual Studio Code 1.0 by provemewrong on Friday April 15, 2016 @01:54AM (#11502495)
My most used editors (Sublime Text and Notepad++) have this.
Re:Visual Studio Code 1.0 by imaginenore on Thursday April 14, 2016 @06:16PM (#11500758)
Notepad++ is a great text editor, but it has no clue about your code base. It can't do searches of all functions, or Ctrl+Click on the method to go to its definition, etc.
Re:Visual Studio Code 1.0 by ChristianGeek on Thursday April 14, 2016 @10:15PM (#11501634)
I dropped Notepad++ for SublimeText a while back (partially because it supports both Windows and Mac). VS Code is slowly winning me over though!
Re:Visual Studio Code 1.0 by smrq on Friday April 15, 2016 @02:07AM (#11502521)
I love ST, but the hotkeys are so different between Windows and Mac and it drives me up the wall. I feel like I'm abroad in the UK and now fries are chips, chips are crisps, crackers are biscuits, Ctrl+H is Cmd+Shift+F, etc... It really gets in the way of my ability to work in my editor fluently, which is ultimately all a text editor is good for.
Re:Visual Studio Code 1.0 by jbrooksuk on Friday April 15, 2016 @03:12AM (#11502726)
You're aware that you can change them right?
Re:Visual Studio Code 1.0 by coldtea on Friday April 15, 2016 @07:25AM (#11503458)
On OS X, download TextWranger -- it's free and close to Notepad++ than TextMate.
Re:Visual Studio Code 1.0 by iSnow on Friday April 15, 2016 @02:05PM (#11506383)
And the best feature of TextWrangler: if it crashes, or the computer shuts down, it remembers unsaved changes in files. Start it up and it restores everything to the last keystroke.

Not sure if other editors do this too.

Re:Visual Studio Code 1.0 by kitd on Friday April 15, 2016 @06:37AM (#11503316)
I'm always surprised that PSPad [1] doesn't get mentioned much in these conversations. I find the built-in utilities are more numerous and work much better than Notepad++. It also handles large files much better IME.

It may be that the customisation is a bit less polished (eg, no way to quickly set themes) and the user community is less developed. But it really does everything and much better than the others IMHO.

[1] - http://www.pspad.com/en/

edit: words

Re:Visual Studio Code 1.0 by Aldo_MX on Friday April 15, 2016 @03:43PM (#11507071)
I prefer to install Notepad2, it uses the same engine as Notepad++ (Scintilla), but I have turned off most options to resemble the stock Notepad:

http://imgur.com/vFu51NV

Re:Visual Studio Code 1.0 by groovy2shoes on Friday April 15, 2016 @10:23PM (#11509001)
So, apart from the icon, how does that resemble Notepad?
Re:Visual Studio Code 1.0 by Aldo_MX on Monday April 25, 2016 @12:03PM (#11565130)
one instance per file, no tabs, no toolbars and a simplified menu (all of that configurable)
Re:Visual Studio Code 1.0 by neves on Thursday April 14, 2016 @04:14PM (#11499977)
I like Notepad++, but I prefer one that works in Windows and in my linux home computer.
Re:Visual Studio Code 1.0 by bitmapbrother on Thursday April 14, 2016 @04:56PM (#11500280)
Notepad++ does work on Linux and also Mac's using WINE.
Re:Visual Studio Code 1.0 by throweway on Thursday April 14, 2016 @05:12PM (#11500389)
Seriously try gvim. Not vim where you need a long ass cheat sheet just to create a new tab or move between splits. But gvim where you can be productive and use the mouse and menus when necessary.
Re:Visual Studio Code 1.0 by klodolph on Thursday April 14, 2016 @05:37PM (#11500535)
The one thing that kills gvim for me is the inability to have one session with multiple windows. I use it anyway.
Re:Visual Studio Code 1.0 by aldanor on Friday April 15, 2016 @04:39AM (#11502975)
Try Emacs with vim bindings and you'll have it, its GUI is a client that connects to a server
Re:Visual Studio Code 1.0 by gcr on Thursday April 14, 2016 @06:52PM (#11500900)
How would that be better than opening multiple gvim processes?
Re:Visual Studio Code 1.0 by klodolph on Thursday April 14, 2016 @07:03PM (#11500947)
I want to type :wa in one window, not four windows. I don't want to get an error message when I try to open a buffer that's already open somewhere else, I want it to just move the buffer to the new window (or alternatively, raise the window containing the buffer). I want to move buffers across windows and keep undo history and register contents. TextMate / Emacs / etc. have this capability, but I can't figure out how to do it in vim.