unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sharon Kimble <boudiccas@skimble.plus.com>
To: help-gnu-emacs@gnu.org
Subject: Re: flycheck on Emacs24
Date: Fri, 02 May 2014 18:51:12 +0100	[thread overview]
Message-ID: <874n18cbn3.fsf@skimble.plus.com> (raw)
In-Reply-To: <87y4yk86f4.fsf@haines.att.net> (haines@haines.att.net's message of "Fri, 02 May 2014 12:57:35 -0400")

[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]

haines@haines.att.net writes:

> Thanks for the help. It led to find out about ELPA. While I was at 
> it I also modularized my emacs init file. That all worked out nicely,
> although it seems gnus init file is no longer auto-line wrapping.
>
> But the bottom line is that I used ELPA to install flycheck. It 
> seems to have succeeded at least to the extent it shows up as a minor 
> mode when I display a file. How to use it I have yet to look into
> because it does not produce the dramatic colored highlight of 
> flymake (I see there is an ELPA package to colorize, and I may 
> try that).

Put this in your ".emacs" -
--8<---------------cut here---------------start------------->8---
(require 'flycheck)
(global-flycheck-mode 1)
--8<---------------cut here---------------end--------------->8---
That will make it work in every buffer with whatever document/text
you’re working with. 
>
> I am worried a bit ELPA's compilation of the package. There was an
> error that it was unable to activate package "f". The required package
> "s-1.7.0" is unavailable. When I look at s.el, I find :
>
>   s-buffer is an installed package.
>   Status: Installed in 
>      `/home/haines/.emacs.d/elpa/s-buffer-20130605.1424/'.
>   Version: 20130605.1424
>   Requires: s-1.6.0, noflet-0.0.3
>   Summary: s operations for buffers
>  
> I see that flycheck is no longer displayed in ELPA's package list. 
> I wonder if this is because it is installed? The error makes me 
> also wonder if the flycheck that I managed to compile and install 
> is fully functional, although off hand it seems to be working.

Look right down at the bottom of the package list and you should
see it like here -
╭────
│ flycheck   20140422.657 unsigned   On-the-fly syntax checking (Flymake done right)
╰────
If you're unsure about it try doing *C-s flycheck* in the package
list, then it will search for it, and find all instances of
'flycheck', and if you keep pressing *C-s* it will work through all
it finds until you find the one that you are looking for. Sounds
long-winded but it works.

Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.4.50.16

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2014-05-02 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 20:54 flycheck on Emacs24 haines
2014-05-02  0:18 ` Sharon Kimble
2014-05-02  7:14 ` Eli Zaretskii
     [not found] ` <mailman.472.1398989910.1147.help-gnu-emacs@gnu.org>
2014-05-02 16:57   ` haines
2014-05-02 17:51     ` Sharon Kimble [this message]
2014-05-04  9:39     ` Sebastian Wiesner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874n18cbn3.fsf@skimble.plus.com \
    --to=boudiccas@skimble.plus.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).