July 16th, 2013

See Also: part 1, part 2


An attempted install on my home system went much more smoothly, all modules appeared to be present. I ran into one remaining issue that I had encountered previously, and so I’ve opened a ticket.


I also discovered the Emacs Guide — which bills itself as an Emacs guide written for JavaScript coders. It’ll cover installation, basic text editing to taking advantage of powerful extensions made for NodeJS and JavaScript. However, it’s primarily a guide to emacs.js, and is currently incomplete (“Creating Modules”, “Creating HTML Files”, “Debugging” and “See Also” are empty sections, while “Creating Projects” exists only as a keybinding note).


Still, I’ve got some other issues with it.


By default, the code wants all of the files in the HOME directory. I don’t put my files they’re — they’re going into Dropbox, and shared across a couple of installs.

It’s not difficult to update the code for this — but if that file is updated in the project, my updates go out the window.

I think the project should support something different, but I haven’t written a replacement for it.


A minor issue is relative line-numbers. I’m sure somebody likes them. I find them distracting.


But most importantly, basic keystrokes are remapped. That the arrow-keys are mapped to other functions is perhaps forgiveable — Emacs already has line-up, line-down, prevchar, next-char mapped to certain keys. Which I never use. Because it’s stupid to use those keystrokes on a modern keyboard that has arrow keys. But, hey. I can almost follow along. Emacs-stylee, right? Although how following an obscure Emacs convention for a library that is pitched at non-Emacs-users who want a Javascript IDE is a bit perplexing.


Unforgiveable, however, is the remapping of keystrokes like kill-region. That’s a basic Emacs keybinding, and shouldn’t be screwed around with. WTF?


emacs.js has the ability too use customized profiles, but these seem to be loaded AFTER things have already been loaded, so the keybindings might be unfixable by simple means. Or maybe it is an easy fix — I haven’t really looked into the customization yet.


I want to use emacs.js — it’s got a lot of javascript-editing packages included that I’m interested in.

But the setup, lack of complete documentation, and bizarre keybindings is slowing me down.

It’s an open-source project, and I can work to minimize those problems.

I’ve opened one ticket already; these notes are part of my own further process.



May 17th, 2013

See Part One


I tried to run init.el from within my existing emacs, but got an error, so I launched it suppressing my config-files

emacs -q -l d:homeemacs.jsinit.el


Basically got the following error (although with a longer trace indicating where it had occured):

Debugger entered--Lisp error: (invalid-function (tool-bar-mode -1))
  ((tool-bar-mode -1) (menu-bar-mode -1) (scroll-bar-mode -1))
  (if window-system ((tool-bar-mode -1) (menu-bar-mode -1) (scroll-bar-mode -1)))
  eval((if window-system ((tool-bar-mode -1) (menu-bar-mode -1) (scroll-bar-mode -1))))
  call-interactively(eval-last-sexp nil nil)


The root seems to be THIS snippet that doesn’t like to work from appearance.el


(if window-system
    ((tool-bar-mode -1)
     (menu-bar-mode -1)
     (scroll-bar-mode -1)))


Now, each of those lines can execute individually, but none of them like to execute in that block.

Why is that?


Oh, my elisp-fu is woefully faded.


hrm. THIS seems to work:


(if window-system
    (progn (tool-bar-mode -1)
           (menu-bar-mode -1)
           (scroll-bar-mode -1)))


so. I update that.



set-default-font: Font Inconsolata-12′ is not defined





End Part Two


read Part One


May 17th, 2013

I’m still trying to figure out how I should be using my wiki and my blog – what content goes where?

I’ve been putting a lot more this-is-what-I-did notes into the wiki, and cleaning them up as I redo it/find other/better ways.

I’m going to try putting them HERE in the blog first (in pmwiki-markup), and then clean them up a bit for the wiki.


That’s the idea, anyway….


This is Part One; read Part Two



So, I decided to test-install emacs.js


NOTE: the installation instructions presume Linux. Because: 1337. Because: Us windows users suck.

Or something like that.


NOTE: the notes below are pretty much unedited transcripts of my attempts to get this to work. They are more a reflection on my unfamiliarity with cygwin than they are of the lack of Windows installation docs. Although making this into an ELPA package would solve this problem in one fell swoop.

read more…

  • syndicate

    • Add to MyMSN
    • Add to MyYahoo
    • Add to Google Reader
    • Add to Bloglines
    • Add to Newsgator
    • Add to NewsIsFree