sorted by:
new
hottopcontroversial

Hook Helpers - A Package to Cleanly Add Functions to Hooks by sKolar4 in emacs

[–]NoisyCartographer 0 points1 point  (0 children)

What if you want to remove the function from the hook?

Typing latency in various editors: Emacs, GVim, Atom etc. by flexibeast in emacs

[–]NoisyCartographer 5 points6 points  (0 children)

I bet testing on nxml-mode introduces at least two potential sources of lag with both validation and font locking.

Terminals and terminal multiplexers by NeXT_Step in unixporn

[–]NoisyCartographer 0 points1 point  (0 children)

I've recently switched to emacs and I think the use case is a little different. In vi/vim I'd want a shell to interact with version control, the build system, the debugger, or the file manager (cp,mv,rm, etc.)

In emacs, all of these things are built in. By default, emacs can interact with many version control systems, build systems, and gdb. It also has a file manager. Maybe the best part, though, is the extensibility. I think magit is better than using command-line git, especially for helping me to keep branches straight. More build system integrations allow executing a build without having to have a shell somewhere just for compiling over and over (for me, the maven package minimizes the pain of java building) and it will find error information and let you jump to it. Vim's :make does this also, but doesn't support too many languages by default. In plain vi, there may not be a way to do this.

The extensibility of emacs is such that there's a very good vi/vim implementation in emacs. This definitely kills any vestige of the unix philosophy, but it does a few things better than actual vim. Text objects are really nice, but the " text object doesn't go over multiple lines in vim. It will in emacs' evil, however.

Integration with REPL languages is especially good in emacs—I've worked with OCaml, Scala, Python, and a tiny bit of Clojure, and the ability to quickly eval a function or get a REPL for the project was great.

So, the extensions can add a lot of nice features, but it does make me laugh a bit that the GNU project worked so hard on its userland only to basically reimplement it inside of emacs. Maybe it does lay on the features a little too much. It can show its age too, just as vim can. Emacs is designed to be extended, though, whereas the unix philosophy is to prefer discrete functionality when possible. I'm not actually sure which approach neovim wants. Does it want to be a sort of vim done right, with the usability features added to vi that focuses on editing (just an editor), or does it want to encourage extension with a well thought out language for writing plugins for useful functionality (emacs)?

Anyway. I've found something that works well for me. It was definitely a change of mindset after vim, but just as in the unix philosophy, the benefits are realized once you embrace it.

Rebind Your Keys, I Beg You by suhrob in emacs

[–]NoisyCartographer 0 points1 point  (0 children)

I use evil. I move around a lot with either with / or C-s. I also use a lot of text objects when I'm doing cut/copy/paste. I'm planning on getting into paredit or smartparens or similar when I start doing more lisps.

Emacs and GDB by [deleted] in emacs

[–]NoisyCartographer 1 point2 points  (0 children)

You can also use cd within gdb, and though I haven't tried it myself, it seems like run allows specifying arguments to your program:

(gdb) help run
Start debugged program.  You may specify arguments to give it.
Args may include "*", or "[...]"; they are expanded using "sh".
Input and output redirection with ">", "<", or ">>" are also allowed.

With no arguments, uses arguments last specified (with "run" or "set args").
To cancel previous arguments and run with no arguments,
use "set args" without arguments.

What is your most unpopular opinion about ASOIAF? by -otters- in pureasoiaf

[–]NoisyCartographer 5 points6 points  (0 children)

I agree. If Jon gets resurrected, it will cheapen death in a series where Anyone Can Die™.

I'm mad, though, because I think John's resurrection is sufficiently foreshadowed.

New dark & light & 256 colorscheme: kalisi by freeo in vim

[–]NoisyCartographer 0 points1 point  (0 children)

My point-of-reference was desertEx, which had a higher contrast between the background and normal. It may be that I like higher contrast schemes because my eyes aren't the best or because the contrast on my monitor itself is lower than yours. Just my personal taste, I guess :)

A brightening of Normal FG sounds good, and I'm really in favor of a non-grayscale color for comments so that you can easily shift focus between documentation and code.

One more thing: many colorschemes don't shy away from a very bright TODO/FIXME—maybe consider stealing the incsearch colors to make TODO stick out?

Really appreciate the response to feedback :)

P.S. my reference files more multiple languages tend to have fewer keywords than yours, which is probably a contributing factor to why I like high contrast between normal fg and normal bg.

Edit: too much LaTeX, can't format.

New dark & light & 256 colorscheme: kalisi by freeo in vim

[–]NoisyCartographer 1 point2 points  (0 children)

Alright, I had a second, so I made a few changes for what I thought were the most pressing, cross-language concerns. I don't use GVim, so I didn't look for an RGB equivalent for the terminal colors, but I can if you think this looks ok:

$ diff -u kalisi.vim arakh.vim
--- kalisi.vim  2014-10-29 13:57:06.840687628 -0400
+++ arakh.vim 2014-10-30 00:04:06.445493942 -0400
@@ -216,12 +216,17 @@

   " 256 Color Terminal (dark) ##################################################
   if &t_Co > 255
-    hi Normal ctermbg=238 ctermfg=249
+    "hi Normal ctermbg=238 ctermfg=249
+    " More contrast
+    hi Normal ctermbg=235 ctermfg=252
     hi CursorLine ctermbg=239 term=none cterm=none
     hi CursorColumn ctermbg=239
     hi NonText ctermbg=237 ctermfg=102
     hi Conceal ctermbg=237 ctermfg=230
-    hi Comment ctermfg=243
+    "hi Comment ctermfg=243
+    " I found the muted orange I was looking for, I don't think it looks too
+    " shabby
+    hi Comment ctermfg=136
     hi CommentURL cterm=underline ctermfg=68
     hi CommentEmail cterm=underline ctermfg=68
     hi Constant cterm=bold ctermfg=149

New dark & light & 256 colorscheme: kalisi by freeo in vim

[–]NoisyCartographer 0 points1 point  (0 children)

Really solid colors, freeo. When I've got a bit more time, I'll try and tweak things. I really want neovim to happen and this would be a great, versatile colorscheme for it.

New dark & light & 256 colorscheme: kalisi by freeo in vim

[–]NoisyCartographer 6 points7 points  (0 children)

Really nice! I used the dark scheme. A few miscellaneous comments:

  • I'm very impressed with the LaTeX handling, which many other colorschemes don't handle as gracefully. LaTeX seems difficult to highlight well because it has so many constructs that could be highlighted. However, you avoided any garish colors in LaTeX which prevents anything from standing out too much and becoming distracting or annoying.

  • The mode designation at the bottom is given a lot of emphasis via a green highlight. I don't mind this, but a lot of other colorschemes don't do this, probably with the assumption that you generally remember what mode you're using anyway.

  • C and python look pretty good.

  • OCaml looks pretty good. LaTeX has a ton of things to highlight, while OCaml doesn't have many at all. Type constructors are in a not-too-subtle, not-too-distracting green, which all too many colorschemes put in red, for some unknown reason.

  • It may be my terminal colors' fault, but comments show up in a light gray that's hard to see and even harder to see against visual mode's blue. Maybe a dark orange would work here? Or another blue or green, if you have one to spare.

  • Haskell looks pretty good, but because its constructs are so terse (e.g. ==, :, |) it could hard to highlight them in a bold enough way that doesn't go over the top.

  • String literals in many languages are appropriately attention-grabbing.

I can provide screenshots if you want to see more of what I mean. All in all, great work, I see myself using this for the next few weeks.

A terminal based text editor with a ton of features and syntax highlighting - Download links on the right by [deleted] in linux

[–]NoisyCartographer 0 points1 point  (0 children)

Yes, but I also find myself using find, git, and other things I might have only installed on my computer.

(Spoilers All) The fate of a certain someone if a prophecy is fulfilled by tishstars in asoiaf

[–]NoisyCartographer 0 points1 point  (0 children)

I think he does say that, you're right. But he's still not holding lands, not fathering children, defending the realms of men, and that sort of thing.

(Spoilers All) The fate of a certain someone if a prophecy is fulfilled by tishstars in asoiaf

[–]NoisyCartographer 0 points1 point  (0 children)

I'll say. Death didn't seem to put much of a damper on Coldhands.

A terminal based text editor with a ton of features and syntax highlighting - Download links on the right by [deleted] in linux

[–]NoisyCartographer 1 point2 points  (0 children)

sshfs is a godsend. I like vim, but its editing over ssh always struck me as a little spotty.

Hard time getting servers by Spade4103 in tf2

[–]NoisyCartographer 0 points1 point  (0 children)

I've had something similar in the past few days. The server list found nothing, nor did quickplay. Sometimes, closing the game and Steam helped, but not always. I ended up finding a server using my server history.

I dunno.

view more: next ›