zsh-workers
 help / color / mirror / code / Atom feed
From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: some fix for completion functions
Date: 28 Feb 2000 01:34:14 +0900	[thread overview]
Message-ID: <rsqu2iuy589.fsf@crane.jaist.ac.jp> (raw)

This modifies some completion functions.

* `dvips -f <TAB>' completes filenames.  Although the manual says it
  reads a .dvi file from stdin, actually it also reads a file specified as
  an argument.

* `lynx <TAB>' completes .html files at first.

* `xwininfo' has options not specifeid in _xutils: -children and -tree.

Index: Completion/User/_dvi
===================================================================
RCS file: /projects/zsh/zsh/Completion/User/_dvi,v
retrieving revision 1.1.1.5
diff -u -r1.1.1.5 _dvi
--- Completion/User/_dvi	1999/12/01 15:29:43	1.1.1.5
+++ Completion/User/_dvi	2000/02/27 16:19:00
@@ -22,7 +22,7 @@
     '(-X -Y)-D[set resolution]:resolution in dots per inch:' \
     '-e[set maximum character offset]:maximum character offset:' \
     '-E[generate EPSF file]' \
-    '(: -o)-f[read from stdin, write to stdout]' \
+    '(-o)-f[write to stdout]' \
     '-F[append control-D]' \
     '-h[specify additional header file]:postscript header file:_files -g \*.\(\#i\)\(ps\|eps\)' \
     '-i[one file per section]' \
Index: Completion/User/_lynx
===================================================================
RCS file: /projects/zsh/zsh/Completion/User/_lynx,v
retrieving revision 1.1.1.5
diff -u -r1.1.1.5 _lynx
--- Completion/User/_lynx	1999/11/15 12:01:49	1.1.1.5
+++ Completion/User/_lynx	2000/02/27 16:19:00
@@ -37,10 +37,10 @@
   '-head' \
   '-help' \
   '-historical' \
-  '-homepage=:URL: _urls -f' \
+  '-homepage=:URL:->html' \
   '-image_links' \
   '-ismap' \
-  '-index=:URL: _urls -f' \
+  '-index=:URL:->html' \
   '-link=:NUMBER:' \
   '-localhost' \
   '-locexec' \
@@ -95,7 +95,7 @@
   '-version' \
   '-vikeys' \
   '-width=:NUMBER:' \
-  ':url: _urls -f'
+  ':url:->html'
 
 case "$state" in
 restrictions)
@@ -105,5 +105,8 @@
     goto inside_ftp inside_news inside_rlogin inside_telnet jump mail \
     multibook news_post options_save outside_ftp outside_news outside_rlogin \
     outside_telnet print shell suspend telnet_port useragent
+  ;;
+html)
+  _files -g '*.html' || _urls
   ;;
 esac
Index: Completion/X/_xutils
===================================================================
RCS file: /projects/zsh/zsh/Completion/X/_xutils,v
retrieving revision 1.1.1.6
diff -u -r1.1.1.6 _xutils
--- Completion/X/_xutils	2000/02/04 12:14:11	1.1.1.6
+++ Completion/X/_xutils	2000/02/27 16:19:00
@@ -8,7 +8,7 @@
   ;;
 xwininfo)
   _x_arguments \
-    -{help,int,stats,bits,events,size,wm,shape,frame,all,english,metric} \
+    -{help,int,children,tree,stats,bits,events,size,wm,shape,frame,all,english,metric} \
     '(-id -name)-root' \
     '(-id -root)-name:name: _x_window -n' \
     '(-name -root)-id:id: _x_window'
-- 
Tanaka Akira


                 reply	other threads:[~2000-02-27 16:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to=rsqu2iuy589.fsf@crane.jaist.ac.jp \
    --to=akr@jaist.ac.jp \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).