Re: data/CVE/list color

2015-10-31 Thread Guido Günther
Hi,
On Sat, Aug 15, 2015 at 12:17:44PM +0200, Moritz Mühlenhoff wrote:
> On Wed, Aug 12, 2015 at 06:23:25PM +0200, Guido Günther wrote:
> > Hi,
> > I wanted some color in debian/CVE/list so I hacked up some very simple 
> > highlighting
> > for emacs:
> > 
> > 
> > https://git.sigxcpu.org/cgit/emacs-tools/commit/?id=200d437c93536d911da85e080188fc68a5221122
> > 
> > I do wonder if there is something else around already and I just did not
> > spot it?
> 
> I'm adding debian-security-tracker@ldo to CC, since not everyone reads 
> debian-lts.
> 
> Nice! I had toyed around with a minor mode for emacs some years ago (to easily
> create NOT-FOR-US enties, but never actually started to use it since I ran 
> into
> some underdocumented elisp areas.. I'll check where I put that code and will
> try to integrate that again.
> 
> > If not, should we add this to the secure-testing repo?
> 
> Please do. Maybe we can merge it into debian-el at a later point.

For what it's worth I've also added some basic indentation:

 
https://git.sigxcpu.org/cgit/emacs-tools/commit/?id=4796b34454d6b3b29a479ef073328b70a0c0568b

so that hitting tab indents CVE-* to column 0 and everuthing to column 8.

I'm not much of a emacs hacker so improvements are certainly
welcome. I'll add this to conf/cvelist.el as well if there are no
objections.

Cheers,
 -- Guido



Re: data/CVE/list color

2015-08-15 Thread Moritz Mühlenhoff
On Wed, Aug 12, 2015 at 06:23:25PM +0200, Guido Günther wrote:
 Hi,
 I wanted some color in debian/CVE/list so I hacked up some very simple 
 highlighting
 for emacs:
 
 
 https://git.sigxcpu.org/cgit/emacs-tools/commit/?id=200d437c93536d911da85e080188fc68a5221122
 
 I do wonder if there is something else around already and I just did not
 spot it?

I'm adding debian-security-tracker@ldo to CC, since not everyone reads 
debian-lts.

Nice! I had toyed around with a minor mode for emacs some years ago (to easily
create NOT-FOR-US enties, but never actually started to use it since I ran into
some underdocumented elisp areas.. I'll check where I put that code and will
try to integrate that again.

 If not, should we add this to the secure-testing repo?

Please do. Maybe we can merge it into debian-el at a later point.

Cheers,
Moritz