Re: output.activate grabs too much text.

On Thu, 23 Oct 2008 15:27:57 -0500
Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:

> One of the ideas for using output.activate is when using egrep to find 
> files, or from diagnostic information reporting filenames.
> 
> For example,   I execute 'egrep lpi *' and get
> ...
> vr_axi_lpi.e:   event lpi_clk_f;
> vr_axi_lpi.e:   event lpi_clk_r;
> vr_axi_lpi.e:   on lpi_clk {
> 
> If I click (output.activate) on vr_axi_lpi.e in the output pane, I get:
> 
> Cannot get information about vr_axi_lpi.e:   event

gtk_text_iter_forward_word_end() skips from
  vr_axi_lpi.e:   event 
             ^
straight to
  vr_axi_lpi.e:   event 
                      ^
so the whitespace after ':' is not detected. Even if you did want the ':'.

> 
> Maybe it would be good to control the accumulation of characters via a 
> list of legal characters that make up a filename. That way one could 
> modify the list if desired.
This starts to get messy. Strictly, anything is 'legal', though some chars are 
definitely unwise.

I'll investigate other workarounds too.

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: