Your message dated Tue, 29 Nov 2011 22:18:26 +0000
with message-id <[email protected]>
and subject line Bug#220581: fixed in gtypist 2.9.1-1
has caused the Debian Bug report #220581,
regarding gtypist: VIM syntax highlighting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
220581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=220581
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: gtypist: VIM syntax highlighting.
Package: gtypist
Version: latest
Severity: wishlist
Tags: patch
In short, I've attached the following things to the report: the syntax file
itself
(it can be obtained from http://home.t-online.de/~fam.natter/gtypist.vim)
and a script that will try to patch the manual (I've resurrected the chapter
from CVS attic and made some editing on it). The
script is to be run from the documentation source directory before
building the documentation. For me it was just an exercise in Perl
programming, I believe there is an easier way to do the patch.that'll work
even on a modified documentation relying on a several conditions (I'd like to
learn them but don't know where to start).
When I wrote the documentation patch I assumed that gtypist.vim will go in
/usr/share/gtypist/. If it will not, then please correct the patch.
--- Dmitry Rutsky
#! /usr/bin/perl -w
#
# A simple script to add VIM mode information to the documentation.
#
my $victim = 'gtypist.texi';
my $backups_count = (system "let a=0;
for i in `find . -name \"$victim.backup*\" -print`;
do let a++;
done; exit \$a") >> 8;
if ($backups_count == 0) { $backups_count = ""; }
my $backup = $victim.".backup".$backups_count;
system "cp $victim $backup";
# These data may require correction.
my $previous_menu_line =
"* Emacs mode:: Emacs mode for editing gtypist scripts\n";
my $added_menu_line =
"* VIM Syntax highlighting:: VIM Syntax highlighting for gtypist scripts\n";
my $previous_node_line =
"\@node Emacs mode, Environment Variables, Create new lessons, Top\n";
my $new_previous_node_line =
"\@node Emacs mode, VIM Syntax highlighting, Create new lessons, Top\n";
my $new_node =
'@node VIM Syntax highlighting, Environment Variables, Emacs mode, Top
@chapter VIM Syntax highlighting@footnote{@emph{Due to some strict GNU policies the Vim editor syntax file isn\'t distributed along with the GNU Typist package. This section of the manual is Debian-specific.}}
@noindent
File @file{/usr/share/gtypist/gtypist.vim} provides syntax highlighting for Vim 5.x and 6.x.
To install it for version 5.x (or any version on DOS/Windows), copy
the file to where the syntax-files go (for example
@file{/usr/share/vim/vim56/syntax/} for Vim 5.6 on Debian 2.2; if everything
else fails you can search for e.g. @file{xml.vim}) and add this to
@file{~/.vimrc} (@file{$HOME/_vimrc} on DOS/Windows):
@example
autocmd BufNewFile,BufRead *.typ set ft=gtypist
@end example
Installation for Vim 6.x is simpler: first create @file{~/.vim/syntax/}:
@code{mkdir -p ~/.vim/syntax} and put @file{/usr/share/gtypist/gtypist.vim} in there.
Finally add this to @file{~/.vimrc}:
@example
autocmd BufNewFile,BufRead *.typ setf gtypist
@end example
In any case, make sure that the @file{vimrc} file has the following command at the top
ahead of all other @code{autocmd}-commands:
@example
autocmd! " Remove ALL autocommands for the current group
@end example
(which avoids problems if @file{vimrc} is sourced more than once).
And if you haven\'t done it already, you need to enable syntax
highlighting:
@example
syntax on " turn on syntax highlighting
@end example
@noindent
All this is also mentioned in the README-section of @file{tools/gtypist.vim}.
';
my $next_node_line =
"\@node Environment Variables, Errors and omissions, Emacs mode, Top\n";
my $new_next_node_line =
"\@node Environment Variables, Errors and omissions, VIM Syntax highlighting, Top\n";
open (INPUT, $backup) or die "Cannot open $backup : $!";
open (OUTPUT, ">$victim") or die "Cannot open $victim for writing : $!";
sub doesnt_work {
close INPUT;
close OUTPUT;
system "mv $backup $victim";
print
"The script has failed, perhaps because some incompatible changes on $victim
had been made. Please correct it accordingly.\n";
exit 1;
}
print OUTPUT "# This file was patched by $0 script.\n\n";
my $state = 0;
while (<INPUT>) {
if ($_ eq $previous_menu_line) {
print OUTPUT $_;
print OUTPUT $added_menu_line;
$state = 1;
}
elsif ($_ eq $previous_node_line) {
unless ($state == 1) { doesnt_work; }
print OUTPUT $new_previous_node_line;
$state = 2;
}
elsif ($_ eq $next_node_line) {
unless ($state == 2) { doesnt_work; }
print OUTPUT $new_node;
print OUTPUT $new_next_node_line;
$state = 3;
}
else {
print OUTPUT $_;
}
}
unless ($state == 3) { doesnt_work; }
close INPUT;
close OUTPUT;
print "Backup stored in $backup.\n";
" Vim syntax file
" Language: GNU Typist script
" Maintainer: Felix Natter <[email protected]> ([email protected])
" URL: http://www.gnu.org/software/gtypist/ (tools/gtypist.vim in the
" source-package)
" Filenames: *.typ
" Last Change: (see ChangeLog below)
" README:
" Installation:
" 'vimrc' is ~/.vimrc on UNIX, and $HOME/_vimrc on DOS/Windows.
" This command should be at the top of your vimrc:
" autocmd! " Remove ALL autocommands for the current group
" (which avoids problems if vimrc is sourced more than once)
" and this should be in there too:
" syntax on " turn on syntax highlighting
"
" vim 5.x:
" copy this file to where the syntax-files go and use this:
" autocmd BufNewFile,BufRead *.typ set ft=gtypist
" (this is also the recommended way to install with vim 6.x on DOS/Windows)
"
" vim 6.x:
" create ~/.vim/syntax:
" $ mkdir -p ~/.vim/syntax
" and put this file in there:
" $ mv gtypist.vim ~/.vim/syntax
" put this in vimrc:
" autocmd BufNewFile,BufRead *.typ setf gtypist
" ChangeLog:
" Sat Oct 20 14:35:44 CEST 2001: initial version
" Sun Oct 21 02:48:24 CEST 2001: use "Error" for gtypistExitCmd
" TODO:
" - E: color number in Float
" For version 5.x: Clear all syntax-items
" For version 6.x: Quit when a syntax-file was already loaded
if version < 600
syntax clear
elseif exists("b:current_syntax")
finish
endif
syn case match
syn keyword gtypistKeyword default Default NULL
" this is necessary so that ':' is not colored
syn match gtypistCmdSeparator ":" contained
syn match gtypistCmd "^[A-Za-z ]:" contains=gtypistCmdSeparator
syn match gtypistExitCmd "^X:" contains=gtypistCmdSeparator
syn match gtypistSetLabelCmd "^\*:" contains=gtypistCmdSeparator
syn keyword gtypistTODO TODO FIXME NOTE XXX contained
syn match gtypistComment "^[#!].*" contains=gtypistTODO
syn region gtypistDrillContent start="^[DdSs]:" skip="^ :" end="^"
contains=gtypistCmd
syn match gtypistLabel "^\*:.*" contains=gtypistSetLabelCmd
syn match gtypistLabelRef "^[GYNF]:.*" contains=gtypistCmd
syn match gtypistKeybind "^K:[0-9]\+:" contains=gtypistCmd,gtypistCmdSeparator
syn match gtypistKeybindLabelRef "^K:[0-9]\+:.*" contains=gtypistKeybind
syn match gtypistBanner "^B:.*" contains=gtypistCmd
if !exists("did_gtypist_syntax_inits")
let did_gtypist_syntax_inits = 1
" note: the links are not very logical (i.e. gtypistLabel != Label),
" because i.e. Label,Keyword look the same (and aren't readable in the GUI)
" write to the maintainer if you know a way to make this more logical
highlight link gtypistKeyword Keyword
highlight link gtypistCmd SpecialChar
highlight link gtypistExitCmd Error
highlight link gtypistComment Comment
highlight link gtypistDrillContent String
highlight link gtypistTODO Todo
" Delimiter looks the same as SpecialChar, so this is commented out
" highlight link gtypistCmdSeparator Delimiter
highlight link gtypistLabel Type
highlight link gtypistLabelRef Include
highlight link gtypistKeybindLabelRef gtypistLabelRef
highlight gtypistBanner term=bold cterm=bold gui=bold
endif
let b:current_syntax = "gtypist"
--- End Message ---
--- Begin Message ---
Source: gtypist
Source-Version: 2.9.1-1
We believe that the bug you reported is fixed in the latest version of
gtypist, which is due to be installed in the Debian FTP archive:
gtypist_2.9.1-1.debian.tar.gz
to main/g/gtypist/gtypist_2.9.1-1.debian.tar.gz
gtypist_2.9.1-1.dsc
to main/g/gtypist/gtypist_2.9.1-1.dsc
gtypist_2.9.1-1_amd64.deb
to main/g/gtypist/gtypist_2.9.1-1_amd64.deb
gtypist_2.9.1.orig.tar.gz
to main/g/gtypist/gtypist_2.9.1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (dale) <[email protected]> (supplier of updated gtypist
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 29 Nov 2011 23:05:12 +0100
Source: gtypist
Binary: gtypist
Architecture: source amd64
Version: 2.9.1-1
Distribution: unstable
Urgency: low
Maintainer: Ben Armstrong <[email protected]>
Changed-By: Daniel Leidert (dale) <[email protected]>
Description:
gtypist - simple ncurses touch typing tutor
Closes: 220581
Changes:
gtypist (2.9.1-1) unstable; urgency=low
.
* New upstream release.
* gtypist.install: Install the gtypist filetype syntax support for vim.
* debian/patches/fix_manual_page_issues.patch: Minor adjustment.
* debian/patches/220581_gtypist_vim_support.patch: Added.
- Install the gtypist filetype syntax support for vim (closes: #220581).
* debian/patches/series: Adjusted.
Checksums-Sha1:
e1937b45d04a03ccd841301704c14b7665860065 1338 gtypist_2.9.1-1.dsc
014be2995a407236124810d6fe4d7bd634a14edd 1562984 gtypist_2.9.1.orig.tar.gz
01049dfa36c83a711412210c0f9aebbc7c02f442 9313 gtypist_2.9.1-1.debian.tar.gz
ab1a74c23e7234e952d91c4442494185279ef0cc 1090844 gtypist_2.9.1-1_amd64.deb
Checksums-Sha256:
f4c2071d3627743a70e1ff12ff571dbcbf61fcb50705e18323d6a924925b3ca6 1338
gtypist_2.9.1-1.dsc
25d52c054ef53f3d0ecbd6934491fe9b966c812f9596778aff757e88c98636a5 1562984
gtypist_2.9.1.orig.tar.gz
01d73d468553c4bdad206f5190102520622ac14e87241065924335e792af60e3 9313
gtypist_2.9.1-1.debian.tar.gz
794bed4f60dc08e547ea3131cd82f1d96842ff3741c13ee4a78b7f7a625bae83 1090844
gtypist_2.9.1-1_amd64.deb
Files:
09161ec1e63c012776a988b1f0f7fa17 1338 misc optional gtypist_2.9.1-1.dsc
8b7e5595fcabd254f85c2e171dcaf4fc 1562984 misc optional
gtypist_2.9.1.orig.tar.gz
a34c15ae82375896c1e2aef9c19208e7 9313 misc optional
gtypist_2.9.1-1.debian.tar.gz
49ca80c4cb22d0bcacd98573c6a8846c 1090844 misc optional
gtypist_2.9.1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEUEARECAAYFAk7VV8UACgkQm0bx+wiPa4wpHgCXfYZbRUk/3+MHvWBSsr08QH/b
9ACgyo9eVWFUdmUDszcE6OOco+ux5Q8=
=443P
-----END PGP SIGNATURE-----
--- End Message ---
