michaelpnash / emacs-for-scala Goto Github PK

Hi,

I am using your emacs configs, and I am thankful. I was wondering why you are not using emacs repositories for plugin install. This can make the whole git branch smaller.

Thanks a lot for your great work on emacs-for-scala!

I guess the init.el should not make assumptions about the platform it is running on.

Debugger entered--Lisp error: (error "Font not available" #<font-spec nil nil Source\ Code\ Pro nil nil nil nil nil 18.0 nil nil nil ((:name . "Source Code Pro-18") (user-spec . "Source Code Pro-18"))>)
  internal-set-lisp-face-attribute(default :font "Source Code Pro-18" #<frame [email protected] 0x116ca78>)
  set-face-attribute(default #<frame [email protected] 0x116ca78> :width normal :weight normal :slant normal :font "Source Code Pro-18")
  set-frame-font("Source Code Pro-18" nil t)
  eval-buffer(#<buffer  *load*> nil "/home/richard/.emacs.d/init.el" nil t)  ; Reading at buffer position 8641
  load-with-code-conversion("/home/richard/.emacs.d/init.el" "/home/richard/.emacs.d/init.el" t t)
  load("/home/richard/.emacs.d/init" t t)
  #[0 "�\205\262

Be warned that init.el fails in Debian Jessie.

This failure imposes an initial and needless barrier for newbies.
Perhaps init.el should be less fancy but more effective.

Warning (initialization): An error occurred while loading `/home/rgomes/.emacs.d/init.el':

error: Font not available, #<font-spec nil nil Source Code Pro nil nil nil nil nil 18.0 nil nil nil ((:name . Source Code Pro-18) (user-spec . Source Code Pro-18))>

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the `--debug-init' option to view a complete error backtrace.

You might want to check out my config for the brace navigation with smart-parens

https://github.com/fommil/dotfiles/blob/master/.emacs.d/init.el#L364

There is a ticket with smart-parens to support virtual parenthesis and we might get round to supporting that at some point as the server can provide that information.

The README looks really nice and catches audience immediately with the screenshot you put on the top. But, it is missing a small session for the complete Emacs dumb and for the impatient.

Something like this below:

For the Impatient

$ git clone http://github.com/michaelpnash/emacs-for-scala
$ mkdir $HOME/.emacs.d
$ cp -b emacs-for-scala/init.el $HOME/.emacs.d
$ emacs

The fonts being employed at the moment look nice, except that variable width fonts in editor windows are very inconvenient for people addicted to rectangular editing.

In my specific situation, I prefer to format the code myself, employing something which looks nice and which helps spotting typos and other stupid mistakes that would be very difficult to spot otherwise.

For example, in the snippet of code below there are 2 typos which are far easier to spot using tabular formatting and fixed width fonts than it would be if using some sort of automatic formatting and variable width fonts.

matrix( 5).populate(gauss.interpolate(i+k+ 5, j+k+base+ 5), rapson.interpolate(i+k+base+ 5))
matrix( 6).populate(gauss.interpolate(l+k+ 6, j+k+base+ 6), rapson.interpolate(i+k+base+ 6))
matrix( 7).populate(gauss.interpolate(i+k+ 7, j+k+base+ 7), rapson.interpolate(i+k+base+ 7))
matrix( 8).populate(gauss.interpolate(i+K+ 8, j+k+base+ 8), rapson.interpolate(i+k+base+ 8))
matrix( 9).populate(gauss.interpolate(i+k+ 9, j+k+base+ 9), rapson.interpolate(i+k+base+ 9))
matrix(10).populate(gauss.interpolate(i+k+10, j+k+base+10), rapson.interpolate(i+k+base+10))
matrix(11).populate(gauss.interpolate(i+k+10, j+k+base+11), rapson.interpolate(i+k+base+11))
matrix(12).populate(gauss.interpolate(i+k+10, j+k+base+12), rapson.interpolate(i+k+base+12))
matrix(12).populate(gauss.interpolate(i+k+10, j+k+base+13), rapson.interpolate(i+k+base+13))
matrix(14).populate(gauss.interpolate(i+k+10, j+k+base+14), rapson.interpolate(i+k+base+14))