9 ms·

Show HN: Komet – Native commit editor for macOS

32 points by zZorgz 10y ago

stephenr 10y ago
Isn't "macOS 10.10" an incorrect name? It's OS X up to 10.11, and then macOS from 10.12 onwards. Regardless, this app is quite nice.
- aaronbrethorst 10y ago
  You're absolutely right, but I think that saying "requires OS X 10.10 - macOS 10.12," or "requires OS X 10.10 - 10.11, or macOS 10.12 or higher" sound weird.
  - stephenr 10y ago
    I would simply say "requires OS X 10.10 or later"
    - zZorgz 10y ago
      Apple docs have references to eg: "macOS 10.8+" regarding SDK version. This may still be up in the air, but I predict it will be natural eventually to just use macOS everywhere.
      - stephenr 10y ago
        Wow really? I've never seen that in user facing information (eg they kept using "Mac OS X" for older versions when they dropped the "Mac" a few years ago
        zZorgz 10y ago
        I was referring to technical developer documentation, but I don't think user facing info will be that much revealing until after 10.12 is released. I say that I predict using macOS will be "natural", although that doesn't necessarily mean it'll be "technically correct" for older versions.
OJFord 10y ago
> Not being stuck in a save-and-close model, applying a > commit takes only one action Uh... `:wq`?
- dmytrish 10y ago
  `:x` may be useful, if "save-and-close" is a problem.
  - pvdebbe 10y ago
    Or normal mode ZZ
- zZorgz 10y ago
  "<escape> colon w q <return>" is too many 'actions' for me personally (and anything that needs me to reach to escape is really asking for it), and I sometimes even mess that combination up (I used vim before using Komet). I learned about :x recently which is only just slightly better, but not in my muscle memory yet. Then one may need to decide when to use q! or cq to discard.. I also prefer using a native editor and am more productive with spell checking and auto correction, surprisingly. edit: I'm also not a user that uses the keyboard all the time. After using Komet, I am surprised how often I actually used the mouse to hit commit instead.
  - OskarS 10y ago
    I use Vim for regular development and has mapped <Space> to colon in normal mode, so for me it feels very much like a single action to just tap those three keys in quick succession with different fingers on one hand then tapping <Enter> with the other hand. It's like executing a fighting-game combo, the muscle memory makes it feel like a single action even though you're hitting several keys. But it's arguably true that Vim is the wrong choice as the default commit editor since the majority of users probably will not feel very comfortable in that environment. In hindsight, nano would probably have been the better choice for default. However, since I'm already a heavy Vim user (and have the vim-fugitive plugin installed), I would never go for anything else.
andruby 10y ago
Do you know GitX? It's perfect for quick git commits with line-by-line staging and unstaging. [0] Up to date fork: https://rowanj.github.io/gitx/ https://rowanj.github.io/gitx/ [1] Original: http://gitx.frim.nl/ http://gitx.frim.nl/
- okket 10y ago
  Last commit: "Nov 10, 2014" https://github.com/rowanj/gitx/commits/master https://github.com/rowanj/gitx/commits/master
- zZorgz 10y ago
  Haven't really checked it out but if it's like git GUI, then it's probably too heavy weight to my liking to use on a daily basis. (personal nitpick: I'd love if the app showed me how to use it rather than having to consult to online instructions)
dsego 10y ago
editor = subl -n -w
- zZorgz 10y ago
  Tried this before making Komet but from what I tested I found this to be slow (stuck in save-and-close model) and obstructive (can bring other sublime documents active).
the_mitsuhiko 10y ago
Not sure how that is better than rendering the editor in the terminal. It's not like you can use that terminal for anything else anyways because it's now waiting for that GUI editor to close.
- zZorgz 10y ago
  On the contrary, I've found keeping the terminal history visible while making commits to be a useful reference.
jbb555 10y ago
Doesn't macos have vim then?
maksymddd 10y ago
What don't just use GitKraken?

32 points by zZorgz 10y ago

Isn't "macOS 10.10" an incorrect name? It's OS X up to 10.11, and then macOS from 10.12 onwards. Regardless, this app is quite nice.

aaronbrethorst 10y ago
You're absolutely right, but I think that saying "requires OS X 10.10 - macOS 10.12," or "requires OS X 10.10 - 10.11, or macOS 10.12 or higher" sound weird.
- stephenr 10y ago
  I would simply say "requires OS X 10.10 or later"
  - zZorgz 10y ago
    Apple docs have references to eg: "macOS 10.8+" regarding SDK version. This may still be up in the air, but I predict it will be natural eventually to just use macOS everywhere.
    - stephenr 10y ago
      Wow really? I've never seen that in user facing information (eg they kept using "Mac OS X" for older versions when they dropped the "Mac" a few years ago
      - zZorgz 10y ago
        I was referring to technical developer documentation, but I don't think user facing info will be that much revealing until after 10.12 is released. I say that I predict using macOS will be "natural", although that doesn't necessarily mean it'll be "technically correct" for older versions.

OJFord 10y ago

> Not being stuck in a save-and-close model, applying a > commit takes only one action Uh... `:wq`?

dmytrish 10y ago
`:x` may be useful, if "save-and-close" is a problem.
- pvdebbe 10y ago
  Or normal mode ZZ
zZorgz 10y ago
"<escape> colon w q <return>" is too many 'actions' for me personally (and anything that needs me to reach to escape is really asking for it), and I sometimes even mess that combination up (I used vim before using Komet). I learned about :x recently which is only just slightly better, but not in my muscle memory yet. Then one may need to decide when to use q! or cq to discard.. I also prefer using a native editor and am more productive with spell checking and auto correction, surprisingly. edit: I'm also not a user that uses the keyboard all the time. After using Komet, I am surprised how often I actually used the mouse to hit commit instead.
- OskarS 10y ago
  I use Vim for regular development and has mapped <Space> to colon in normal mode, so for me it feels very much like a single action to just tap those three keys in quick succession with different fingers on one hand then tapping <Enter> with the other hand. It's like executing a fighting-game combo, the muscle memory makes it feel like a single action even though you're hitting several keys. But it's arguably true that Vim is the wrong choice as the default commit editor since the majority of users probably will not feel very comfortable in that environment. In hindsight, nano would probably have been the better choice for default. However, since I'm already a heavy Vim user (and have the vim-fugitive plugin installed), I would never go for anything else.

andruby 10y ago

Do you know GitX? It's perfect for quick git commits with line-by-line staging and unstaging. [0] Up to date fork: https://rowanj.github.io/gitx/ https://rowanj.github.io/gitx/ [1] Original: http://gitx.frim.nl/ http://gitx.frim.nl/

okket 10y ago
Last commit: "Nov 10, 2014" https://github.com/rowanj/gitx/commits/master https://github.com/rowanj/gitx/commits/master
zZorgz 10y ago
Haven't really checked it out but if it's like git GUI, then it's probably too heavy weight to my liking to use on a daily basis. (personal nitpick: I'd love if the app showed me how to use it rather than having to consult to online instructions)

dsego 10y ago

editor = subl -n -w

zZorgz 10y ago
Tried this before making Komet but from what I tested I found this to be slow (stuck in save-and-close model) and obstructive (can bring other sublime documents active).

the_mitsuhiko 10y ago

Not sure how that is better than rendering the editor in the terminal. It's not like you can use that terminal for anything else anyways because it's now waiting for that GUI editor to close.

zZorgz 10y ago
On the contrary, I've found keeping the terminal history visible while making commits to be a useful reference.

jbb555 10y ago

Doesn't macos have vim then?

maksymddd 10y ago

What don't just use GitKraken?