zsh-workers
 help / color / mirror / code / Atom feed
* 'loop' vs 'loop=device' in _mount
@ 2009-08-26 22:03 Benjamin R. Haskell
  2009-08-27 20:37 ` Peter Stephenson
  0 siblings, 1 reply; 3+ messages in thread
From: Benjamin R. Haskell @ 2009-08-26 22:03 UTC (permalink / raw)
  To: zsh-workers

When using completion for mount options, I often run into the annoyance 
that the 'loop' option prompts for the loopback devide to use.  Really, 
though, one needn't specify any device in particular...  Says the man-page 
for 'mount':

'''
If no explicit loop device is mentioned (but just an option `-o loop' is 
given), then mount will try to find some unused loop device and use that.
'''

I'll likely just patch my own completion script to change:

Completion/Unix/Command/_mount, line 325:
-      'loop[use loopback device]:loopback device:_files'
+      'loop[use loopback device]'

since I couldn't tell how to incorporate an '-o' option that accepts an 
optional argument.  But, I also figured I'd mention it here in case 
someone with better completion-fu could work out a simple patch to correct 
the behavior (which is a bug for certain values of bug).

Best,
Ben


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 'loop' vs 'loop=device' in _mount
  2009-08-26 22:03 'loop' vs 'loop=device' in _mount Benjamin R. Haskell
@ 2009-08-27 20:37 ` Peter Stephenson
  2009-08-28 14:59   ` Benjamin R. Haskell
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Stephenson @ 2009-08-27 20:37 UTC (permalink / raw)
  To: zsh-workers

On Wed, 26 Aug 2009 18:03:32 -0400 (EDT)
"Benjamin R. Haskell" <zsh@benizi.com> wrote:
> When using completion for mount options, I often run into the annoyance 
> that the 'loop' option prompts for the loopback devide to use.  Really, 
> though, one needn't specify any device in particular...  Says the man-page 
> for 'mount':
> 
> '''
> If no explicit loop device is mentioned (but just an option `-o loop' is 
> given), then mount will try to find some unused loop device and use that.
> '''
> 
> I'll likely just patch my own completion script to change:
> 
> Completion/Unix/Command/_mount, line 325:
> -      'loop[use loopback device]:loopback device:_files'
> +      'loop[use loopback device]'
> 
> since I couldn't tell how to incorporate an '-o' option that accepts an 
> optional argument.

It should be just a question of doubling the first colon, as follows
(see the documentation for _values).  However, I couldn't get the suffix
(i.e. the "=") added to be removed when I typed ",", i.e. tried to add a
new list option instead of an argument... until it finally occurred to
me after an astonishing amount of looking in completely the wrong place
that I hadn't told it when to remove it (patch to _values---so non-final
optional arguments to values were always a bit inconvenient).

The following should do more or less what you want; the behaviour is
like that after "/" in file names, but the "," will cause the
auto-remove behaviour of the "=", too.

Index: Completion/Base/Utility/_values
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Utility/_values,v
retrieving revision 1.11
diff -u -r1.11 _values
--- Completion/Base/Utility/_values	13 Jan 2009 12:19:53 -0000	1.11
+++ Completion/Base/Utility/_values	27 Aug 2009 20:34:30 -0000
@@ -59,7 +59,7 @@
       _describe "$descr" \
         noargs "$sep[@]" -M 'r:|[_-]=* r:|=*' -- \
         args -S "${argsep}" -M 'r:|[_-]=* r:|=*' -- \
-        opts -qS "${argsep}" -M 'r:|[_-]=* r:|=*'
+        opts -qS "${argsep}" -r "${argsep}${sep} \\t\\n\\-" -M 'r:|[_-]=* r:|=*'
 
       curcontext="$oldcontext"
 
Index: Completion/Unix/Command/_mount
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_mount,v
retrieving revision 1.29
diff -u -r1.29 _mount
--- Completion/Unix/Command/_mount	4 Jun 2009 15:32:22 -0000	1.29
+++ Completion/Unix/Command/_mount	27 Aug 2009 20:34:31 -0000
@@ -322,7 +322,7 @@
       '(nosuid)suid[use suid and sgid bits]'
       '(async)sync[do I/O synchronously]'
       'dirsync[perform directory updates synchronously]'
-      'loop[use loopback device]:loopback device:_files'
+      'loop[use loopback device]::loopback device:_files'
       'encryption[enable encryption]:cypher'
       'keybits[set number of bits in encryption key]:key size:(64 128 160 192 256)'
       'offset[specify data start for loopback mount]:offset (bytes)'

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 'loop' vs 'loop=device' in _mount
  2009-08-27 20:37 ` Peter Stephenson
@ 2009-08-28 14:59   ` Benjamin R. Haskell
  0 siblings, 0 replies; 3+ messages in thread
From: Benjamin R. Haskell @ 2009-08-28 14:59 UTC (permalink / raw)
  To: zsh-workers

On Thu, 27 Aug 2009, Peter Stephenson wrote:

> On Wed, 26 Aug 2009 18:03:32 -0400 (EDT)
> "Benjamin R. Haskell" <zsh@benizi.com> wrote:
> > When using completion for mount options, I often run into the annoyance 
> > that the 'loop' option prompts for the loopback devide to use.  Really, 
> > though, one needn't specify any device in particular...  Says the man-page 
> > for 'mount':
> > 
> > '''
> > If no explicit loop device is mentioned (but just an option `-o loop' is 
> > given), then mount will try to find some unused loop device and use that.
> > '''
> > 
> > I'll likely just patch my own completion script to change:
> > 
> > Completion/Unix/Command/_mount, line 325:
> > -      'loop[use loopback device]:loopback device:_files'
> > +      'loop[use loopback device]'
> > 
> > since I couldn't tell how to incorporate an '-o' option that accepts an 
> > optional argument.
> 
> It should be just a question of doubling the first colon, as follows
> (see the documentation for _values).  However, I couldn't get the suffix
> (i.e. the "=") added to be removed when I typed ",", i.e. tried to add a
> new list option instead of an argument... until it finally occurred to
> me after an astonishing amount of looking in completely the wrong place
> that I hadn't told it when to remove it (patch to _values---so non-final
> optional arguments to values were always a bit inconvenient).

Oh, good, I'm not crazy...  I tried doubling the colon (seeing it used 
with '(nocheck)check[...]::checking level:...'), and experienced that 
problem.



> The following should do more or less what you want; the behaviour is
> like that after "/" in file names, but the "," will cause the
> auto-remove behaviour of the "=", too.

Indeed.  This does exactly what I want.

Thanks,
Ben


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-08-28 14:59 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-26 22:03 'loop' vs 'loop=device' in _mount Benjamin R. Haskell
2009-08-27 20:37 ` Peter Stephenson
2009-08-28 14:59   ` Benjamin R. Haskell

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).