zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: _complete_debug and Re: Completion troubles
Date: Tue, 2 May 2000 15:16:48 +0000	[thread overview]
Message-ID: <1000502151648.ZM14068@candle.brasslantern.com> (raw)
In-Reply-To: <390EC0E9.54E0FA69@u.genie.co.uk>

On May 2, 12:50pm, Oliver Kiddle wrote:
}
} > Use _complete_debug, ^X?, and examine the trace file.
} 
} I actually, have nedit aliased to /usr/local/bin/nc and _complete_debug
} had a few problems creating a trace file with lots of slashes in its
} name.

Ooops.

} With the print -zR line in _complete_debug, why is $VISUAL and $EDITOR
} used? Why would anyone want to edit the trace file?

I always want to edit the trace file.  It's much easier to search forward
and backward in most editors than it is in most pagers, and I also find it
helpful to be able to delete (or hide with narrowing in emacs) large parts
of the trace that I have determined to be unrelated to the problem.

} > } The other thing is the _expand completer now seems to be expanding
} > } everything after a tilde which is annoying.
} > 
} > Hmm, that doesn't happen to me;  I get this sort of thing:
} 
} You get what I would expect. Try setting the glob style to a true value.

Ah.  That's a little odd, since `glob' ususally means filename generation
and `~' is filename expansion, but there probably isn't any useful way to
distinguish the two during _expand.

} You're right about substitute being true as being significant. I'm not
} sure that your fix has worked enitiely though - I get an error message
} about the closing brace being expected. What do you get if you do:
} exp='${foo'
} echo $(print -lR - ${(e)exp} 2>/dev/null)

Hmm, I was sure I tested that.  Got the redirection in the wrong place.

--- zsh-forge/current/Completion/Core/_expand	Mon May  1 10:58:58 2000
+++ Completion/Core/_expand	Tue May  2 08:04:07 2000
@@ -39,7 +39,7 @@
   { [[ "$curcontext" = expand-word:* ]] && expr=1 } } &&
     [[ "${(e):-\$[$expr]}" -eq 1 ]] &&
     exp=( ${(f)"$(print -lR - ${(e)exp//\\[ 	
-]/ } 2>/dev/null)"} )
+]/ })"} ) 2>/dev/null
 
 # If the array is empty, store the original string again.
 

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~2000-05-02 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-02 11:50 Oliver Kiddle
2000-05-02 15:16 ` Bart Schaefer [this message]

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=1000502151648.ZM14068@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).