HN user

mattengi

65 karma
Posts4
Comments12
View on HN
  - syntax highlight
  - decent automatic indenting
  - semantic auto completion popup
  - on the fly compile
  - on the fly syntastic check(lint tool)
In vim, those settings are very sluggish in my old AMD 2 core 1Ghz cpu laptop. Sublime Text and Emacs both are quite reasonable.

I think vim could be more responsive.

This slow response problem is only reason for trying other editor. Please make this real.

In linux, if you want to make Capslock as both ESC and Ctrl,

    $ setxkboption -option -option 'ctrl:nocaps'
    $ xcape
https://github.com/alols/xcape

What is good for?

  - Happy with vim
  - Happy with emacs like - readline - keybinding. C-a, C-e, C-u, C-k, C-d, C-h, C-w, C-p, C-n, C-y ...
  - Ctrl key is most used in any gui application.
You can abandon both bottomleft Ctrl and topleft Esc.

In Korea, almost all keyboard is just plain QWERTY keyboard with additional Hangul Printing.[0]

Right Alt key used as Hangul(Korean)/English toggle, right Ctrl key as Hanja.

When toggled to Hangul, only English characters are overridden by Hangul characters. All numbers, symbols are also same when you are in English typing mode.

Basically no additional key in there compared to QWERTY.

Is that complex and hard learning type in Hangul? Nope. Maybe 'Korean' is complex to learn, but 'Hangul' - I mean, script? character composition system? sort of that - is quite simple.[2]

Actually It's capable of implement more efficient input layout than English especially more restricted environment. Like basic cell phone key layout(E.161).[1]

There was a King, and He was really great hacker. Because he was a King, he grabbed bunch of smart guy all around country. ; ) Then push them working hard. (did I said he was King?) Therefore, invented many good one for country people. Today Korean has own quite good and expressive characters and he deserved quite good place.[3]

[0] http://i.imgur.com/j0Xk6oY.jpg

[1] http://bit.ly/11CF0mS

[2] http://blog.naver.com/PostView.nhn?blogId=neraijel&logNo=110...

[3] http://i.imgur.com/69jkSXa.jpg

> Irrespective of whether the app dev uses (1) or (2), they are relying on other people to do work before they can deploy their application. This is less empowering, and for an emerging platform such as Ubuntu, we need to enable app developers to deliver their apps without such delays.

> App Review - When the developer submits a new version of their application, it will go through a series of automated checks to verify that it conforms to the Extras packaging and security rules. The developer will be responsible for ensuring the package works effectively. If it doesn’t, the ratings and reviews will surely reflect this.

> We should not rely on manual reviews of software before inclusion. Manual reviews have been found to cause a significant bottleneck in the MyApps queue and they won’t scale effectively as we grow and open up Ubuntu to thousands of apps.

> The developer will not be able to add any other AppArmor abstractions beyond the ones defined above. All of these options are considered safe, and do not require a manual review before being allowed into the Extras archive. The user will be told about any options from the third group that the application needs, and will be asked to allow or reject its installation.