From: Daniel Leslie d...@ironoxide.ca
Subject: Re: [Chicken-users] using flymake with chicken
Date: Fri, 23 Nov 2012 14:09:34 -0800
Oh excellent!
You may be able to remove the need for the shell script by running
something like:
(shell-command-to-string (format csi -SAv \%s\ || true
Also: is there a way to show the error message? I found
flymake-display-err-menu-for-current-line, but that gives
an annoying popup with the message, which is cut off so you
can't read the most important parts.
Oh, look:
Felix scripsit:
There is nothing like emacs.
'There's nothing like eating hay when you're faint,' he [the White King]
remarked to her [Alice], as he munched away.
'I should think throwing cold water over you would be better,' Alice
suggested: 'or some sal-volatile [smelling-salts, ammonium
On Sat, Nov 24, 2012 at 08:21:05PM +0100, Felix wrote:
Also: is there a way to show the error message? I found
flymake-display-err-menu-for-current-line, but that gives
an annoying popup with the message, which is cut off so you
can't read the most important parts.
Oh, look:
On Fri, Nov 23, 2012 at 08:27:32PM +0100, Peter Bex wrote:
Suggestions are welcome.
Flymake doesn't have default key bindings for going to the next/prev error.
Maybe the mode can set up something like M-n and M-p to step between
errors? Or does it make more sense to let the user do this so
Oh excellent!
You may be able to remove the need for the shell script by running
something like:
(shell-command-to-string (format csi -SAv \%s\ || true option-or-filename))
Thanks,
-Dan
On Fri, Nov 23, 2012 at 11:05 AM, Felix
fe...@call-with-current-continuation.org wrote:
Hello!
