<story><title>Show HN: Ymacs - Emacs in the browser with Dropbox, GDrive, etc</title><url>http://tageorgiou.github.com/ymacs/</url></story><parent_chain><item><author>danielweber</author><text>C-k (the most useful command ever) is captured by my browser. Google Chrome.</text></item><item><author>ajross</author><text>It&apos;s not emacs (I guess it&apos;s &quot;an emacs&quot;).  It&apos;s an editor that does syntax coloring, handles the core emacs keystrokes, and implements the subset of GNU emacs functionality that the author uses in a routine manner.&lt;p&gt;Right off the bat, I hit the following speedbumps:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  + No replace-regexp
  + No set-fill-prefix (or it&apos;s unbound)
  + Default fill prefix detection doesn&apos;t work like GNU emacs (e.g. no
    way to fill a long paragraph with a prefix of &quot;&amp;#62; &quot; for quoting
    email)
  + No ispell-word (or any spell checker) on C-$
  + C-x b tab doesn&apos;t give me the list of buffers I expect
  + No keyboard navigability in file selection dialog!  I hit C-x C-f
    and end up in this weird web 2.0 world where I&apos;m (no joke) prompted to
    &quot;Drag files here&quot;.
&lt;/code&gt;&lt;/pre&gt;
So.. it&apos;s cute.  But other than the author (or someone else willing to reimplement the bits of emacs they need) I don&apos;t see to whom it&apos;s going to appeal.  Serious emacs users aren&apos;t the target demographic.</text></item></parent_chain><comment><author>antimatter15</author><text>I&apos;m inclined to think that that&apos;s more a bug on their part since Ctrl+K isn&apos;t one of those unstoppable key combinations (Ctrl+W, Ctrl+Tab, Ctrl+T, Ctrl+N, Shift+Esc as far as I&apos;m aware are the only ones). Perhaps they just aren&apos;t calling e.preventDefault() on their event handlers.&lt;p&gt;And even for the combinations which can&apos;t be captured, the new Chrome platform app API lets you stop those.</text></comment>
<story><title>Show HN: Ymacs - Emacs in the browser with Dropbox, GDrive, etc</title><url>http://tageorgiou.github.com/ymacs/</url></story><parent_chain><item><author>danielweber</author><text>C-k (the most useful command ever) is captured by my browser. Google Chrome.</text></item><item><author>ajross</author><text>It&apos;s not emacs (I guess it&apos;s &quot;an emacs&quot;).  It&apos;s an editor that does syntax coloring, handles the core emacs keystrokes, and implements the subset of GNU emacs functionality that the author uses in a routine manner.&lt;p&gt;Right off the bat, I hit the following speedbumps:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  + No replace-regexp
  + No set-fill-prefix (or it&apos;s unbound)
  + Default fill prefix detection doesn&apos;t work like GNU emacs (e.g. no
    way to fill a long paragraph with a prefix of &quot;&amp;#62; &quot; for quoting
    email)
  + No ispell-word (or any spell checker) on C-$
  + C-x b tab doesn&apos;t give me the list of buffers I expect
  + No keyboard navigability in file selection dialog!  I hit C-x C-f
    and end up in this weird web 2.0 world where I&apos;m (no joke) prompted to
    &quot;Drag files here&quot;.
&lt;/code&gt;&lt;/pre&gt;
So.. it&apos;s cute.  But other than the author (or someone else willing to reimplement the bits of emacs they need) I don&apos;t see to whom it&apos;s going to appeal.  Serious emacs users aren&apos;t the target demographic.</text></item></parent_chain><comment><author>radarsat1</author><text>That&apos;s actually a pretty big problem with the whole &quot;browser app&quot; thing, isn&apos;t it... there are certain key bindings that you just &lt;i&gt;can&apos;t have&lt;/i&gt;.  I wonder if there&apos;ll ever be a solution for that.  Anything I can think of sounds like it would be a security issue, or annoying.  (Having to answer pages asking for permission for certain keybindings... ugh.)</text></comment>