September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joseph Rushton Wakeling | On Monday, 16 September 2013 at 10:05:05 UTC, Joseph Rushton Wakeling wrote:
> On 16/09/13 07:01, deadalnix wrote:
>> What do you use to do that in vim ? All my attempts did fail.
>
> I use this plugin: http://www.vim.org/scripts/script.php?script_id=231
>
> It's always worked for me.
Nice, I have to give it a try !
|
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to H. S. Teoh | On Friday, 13 September 2013 at 22:11:52 UTC, H. S. Teoh wrote: > On Fri, Sep 13, 2013 at 09:48:05PM +0000, Justin Whear wrote: >> I've introduced a few young developers to Vim and the major hole that >> they tend to fall into is printing out a list of vim "keyboard >> shortcuts", because that's how other editors work: you memorize a >> bunch of arbitrary key combinations. So the thing that I emphasize is >> learning Vim's *language*. > > Mmm, I like that description! You're right, it's actually a language, > not just a bunch of shortcuts. That's why is far more expressive than a > shortcut-based editor. You'd need an exponential number of shortcuts > just to keep up with all the possibilities -- clearly impractical. > I'm surprised this hasn't come up yet: http://stackoverflow.com/a/1220118/432364 Probably one of the more famous SO answers ever. Also, this cheat sheet is pretty much the best: http://www.viemu.com/vi-vim-cheat-sheet.gif -Wyatt |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Namespace | On Friday, 13 September 2013 at 19:48:18 UTC, Namespace wrote:
> Just out of interest.
>
vim. Not vi. Not gvim. vim. With TERM=xterm-256color and a small set of plugins. Sometimes in screen.
-Wyatt
|
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Namespace | Emacs on Arch Linux.
On Friday, 13 September 2013 at 19:48:18 UTC, Namespace wrote:
> Just out of interest.
>
> I use Sublime 2, Notepad++ and as IDE currently Mono-D. But I will try this evening VisualD.
|
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Paulo Pinto | I don't get posts like this. If you just install emacs and don't customise it, then yeah, it's not great. But that's like harshing on zsh for being worse than bash with an empty .zshrc. Who does that anyway? This is why there are several, several .emacs.d repositories on github. Anyway, on to your qualms: > - Semantic refactoring I wish I had this for C++, I really do. There's some work being done right now at Google based on LLVM. But I most definitely do have that for Python with Rope and I've been wanting to install Robe to have the same for Ruby. All of this in emacs BTW. > - WYSIWYG design of user interfaces I'd rather see the code, but to each his/her own. > - code navigation, even across binary modules (call graph, derived class, overridden methods, call sites, ...) Emacs + one or more of the following: ctags, etags, semantic, cscope. > - graphical representation of code relationships Not interesting to me. > - UML design Blergh. > - visual XML tooling Not interesting to me. > - background compilation showing where there are issues > - background static analysis while coding Emacs + flycheck. Supporting ever more languages, and D is one of them! > - code completation with documentation popups Emacs + autocomplete. > - integrate source code control with task management software to track code changes to project tasks Emacs... but I'd rather use the "real" commands in a terminal. > - map failed unit tests to code lines I'm pretty sure this can be integrated in emacs since this is already done if you compile in it. All in all, use what you're most comfortable and productive with. Nearly every single time I read/hear "oh, but editors can't do X" it usually means "I've never seen anyone do X with an editor". Emacs is basically a mini OS anyway. Anything it can't do now can be made to happen by writing more elisp. Atila |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to H. S. Teoh | I wish unix had a recursive user system. Where each user is root of its own little domain. Then each app I install would just be suid to a child user that has access only to its own little installation subdirectory. If it wants to write to my regular home, it can sudo back to my other user. It'd save the dangers of one account for everything that matters (the difference between me and root is fairly irrelevant - if root's files get messed up, I can just reinstall them from the cd. If my files get messed up, that's a real hassle!) |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Wyatt | On Mon, Sep 16, 2013 at 01:28:07PM +0200, Wyatt wrote: > On Friday, 13 September 2013 at 22:11:52 UTC, H. S. Teoh wrote: > >On Fri, Sep 13, 2013 at 09:48:05PM +0000, Justin Whear wrote: > >>I've introduced a few young developers to Vim and the major hole that they tend to fall into is printing out a list of vim "keyboard shortcuts", because that's how other editors work: you memorize a bunch of arbitrary key combinations. So the thing that I emphasize is learning Vim's *language*. > > > >Mmm, I like that description! You're right, it's actually a language, not just a bunch of shortcuts. That's why is far more expressive than a shortcut-based editor. You'd need an exponential number of shortcuts just to keep up with all the possibilities -- clearly impractical. > > > I'm surprised this hasn't come up yet: > http://stackoverflow.com/a/1220118/432364 > Probably one of the more famous SO answers ever. Whoa. Most epic SO answer ever! Thanks for the link, I'm bookmarking it, even if just for posterity. :) > Also, this cheat sheet is pretty much the best: http://www.viemu.com/vi-vim-cheat-sheet.gif [...] Nice, thanks! T -- Your inconsistency is the only consistent thing about you! -- KD |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
On Mon, Sep 16, 2013 at 08:43:00AM +0100, Iain Buclaw wrote: > On Sep 16, 2013 4:50 AM, "H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote: [...] > > GNU screen is pretty awesome. But it has some warts that makes me not use it by default: > > > > - Its default escape sequence is extremely annoying (ctrl-A clashes > > with bash's go-to-beginning-of-line, which I use literally *all* > > the time). Switching it to something like ctrl-U makes it more > > tolerable. > > > > - It doesn't seem to pick up terminal settings correctly sometimes. > > Which results in needing to set $TERM manually, or type > > `TERM=rxvt-unicode program args`, instead of just `program args`. > > Quite annoying. > > > > > > Someone did suggest an alternative to GNU screen that is being actively developed on (GNU Screen is kinda regarded as unmaintainable) but I forget the name of it. [...] Hmm. Now I'm tempted to write a GNU screen clone in D. Could be the next killer D app. ;-) T -- There are two ways to write error-free programs; only the third one works. |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Adam D. Ruppe | On Mon, Sep 16, 2013 at 03:52:21PM +0200, Adam D. Ruppe wrote: > I wish unix had a recursive user system. Where each user is root of its own little domain. That's a neat idea. It's probably not hard to implement in Linux... but I'm no kernel hacker so I wouldn't know where to start. > Then each app I install would just be suid to a child user that has access only to its own little installation subdirectory. If it wants to write to my regular home, it can sudo back to my other user. > > It'd save the dangers of one account for everything that matters (the difference between me and root is fairly irrelevant - if root's files get messed up, I can just reinstall them from the cd. If my files get messed up, that's a real hassle!) True! My older projects are on subversion hosted on a remote server, so that serves as a crude kind of backup, but my newer projects (mostly D stuff) are all on git, and if I lose $HOME, all of them will be gone for good!! Which reminds me... it's probably time to make backups of $HOME again... T -- In order to understand recursion you must first understand recursion. |
September 16, 2013 Re: [OT] Which IDE / Editor do you use? | ||||
---|---|---|---|---|
| ||||
Posted in reply to John Colvin | On Mon, Sep 16, 2013 at 10:07:22AM +0200, John Colvin wrote: > On Monday, 16 September 2013 at 01:55:25 UTC, H. S. Teoh wrote: > >On Sun, Sep 15, 2013 at 07:14:17PM +0200, Dicebot wrote: [...] > >>Not entirely true. You should never have anything not managed by package manager on Linux system, it is a reliable road to disaster. Better distinction is "/usr/" for packages from official repos, "/usr/local" for own custom packages. > > > >Seriously? I installed unmanaged stuff all the time, and never had much of an issue. Though, granted, I never put them under /usr or /usr/local at all. It's usually in a dedicated subdirectory under $HOME. > > > >Installing unmanaged stuff under the /usr tree is tricky business, because when you're trying to *uninstall*, you usually don't remember where all the bits have been scattered, and leaving them lying around can lead to trouble. > > > > > >T > > Ever since watching a friend have his entire /usr deleted by a dodgy 'sudo make install', i desperately avoid manually installing to anywhere but a dedicated subdir in $home. No root access needed and I actually know where everything is =) Yeah, I don't trust random Makefiles I download over the 'Net. I usually put the source trees under /usr/src, which I use mainly for experimental stuff anyway, and since /usr is unwriteable by non-root, the worst a Makefile-gone-wrong can do is to nuke the entire /usr/src, while leaving everything else (esp. the all-important $HOME) intact. These days, though, I hardly ever even run make install anymore. Most apps (that I'm interested in, anyway) can be run as-is from the build directory, or if not, can be manually copied file-by-file to some dedicated target directory (the file list is hand-copied from the output of `make -n`, which also lets me know exactly *what* the thing actually does without actually doing it). Anything more complex than that, and I start weighing how badly I want that app vs. how little I trust it. Usually I don't care badly enough to actually install something that requires running a dodgy Makefile that takes a suspiciously long 20 seconds to install a mere 10-15 files. T -- They say that "guns don't kill people, people kill people." Well I think the gun helps. If you just stood there and yelled BANG, I don't think you'd kill too many people. -- Eddie Izzard, Dressed to Kill |
Copyright © 1999-2021 by the D Language Foundation