Re: Some issues with the newest pre-release (20050526)

On Tue, 14 Jun 2005 20:47:13 -0400
Keith Novelist Fancher <kf54876@xxxxxxxxxxxx> wrote:

> > Here, typing "exit" closes the terminal window (I checked with xterm
> >  and gnome-terminal). Perhaps the next step toward resolution is to 
> > confirm that your button's action is: <custom command> 
> > $[command-xterm] & If so, try changing it to <custom command> sh -c 
> > $[command-xterm] (IIRC, yours will save such change, before it 
> > crashes, or maybe "apply" won't crash) Otherwise, we might find 
> > something from app. versions ??
> 
> Hmm... I guess it must be some kind of aterm issue, actually.  I set
> my terminal to xterm and it worked fine.  I guess I can just use xterm
> as my emelfm2 terminal.  I don't understand what it could be.  I tried
> the above and it still didn't work correctly.  No big deal though.

I see that vte does not close upon an 'exit' command, either. Possibly to do 
with the way the app's are initated ?

> 
> 
> >> 5) Finally: the unpack plugin doesn't seem to work, and it didn't 
> >> work in the previous pre-release either.  I'm not sure about 
> >> anything before that.
> > Works as expected, here, so please provide some more detail about
> > the
> >  nature of the problem.
> 
> I found out that it is actually working, but not refreshing correctly
> after it unpacks.  If I manually click "refresh, I see the unzipped
> files there.
Hmm. Here, it refreshes automatically, at least for the case I tested, which 
put a single 'parent' directory into the temporary directory.

I confess I've never tried to find out exactly what changes trigger, or don't 
trigger, update of a directory's mtime and/or ctime - a change to either of 
those will trigger an automatic refresh.

If you have FAM or gamin (>= 0.1) development files available, compile with the 
relevant option (see the file INSTALL). Gamin does better than timechecks, but 
still not bullet-proof. I've never tried FAM.

  I commented out a e2_filelist_disable_refresh() and it
> seemed to work fine after that, but it kept warning me about how
> auto-refresh was broken and I should exit quickly.
disable and enable always come (or go!) in matched pairs ...

  Oh, and it doesn't
> go back to the original directory after you choose to delete or repack
> the items, it just stays in /tmp.  Didn't it used to pop back to
> whatever directory you were in before?
The "what to do" dialog is triggered when you leave the temp-directory where 
the upacked files are located. After deleting/re-packing, the displayed 
directories should stay as they were, i.e. one of them will be where you 
changed to, immediately before the dialog. If that was the temp-directory 
parent (which may be /tmp), then so be it.

> 
> Oh yeah, one more thing about Plugin:unpack: to extract standard zip
> files on many (most?) systems you have to call "unzip" instead of
> gunzip.  I changed the "gunzip -f" to "unzip -o" and re-made and
> re-installed and that made it work for zips on my system.  Maybe a way
> to change the unzip/zip command on a per-system or per-user basis?  I
> dunno.
Reverted to (un)zip commands in the unpack plugin. Perhaps another time someone 
will add a runtime test for whether to use g(un)zip instead.

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: