topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday March 28, 2024, 11:58 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: [bugs report] here is a list of outstanding bugs  (Read 7736 times)

nitrix-ud

  • Charter Member
  • Joined in 2005
  • ***
  • default avatar
  • Posts: 560
    • View Profile
    • Donate to Member
[bugs report] here is a list of outstanding bugs
« on: October 15, 2007, 12:13 PM »
Mouser asked me to post a list of outstanding bugs regarding FARR
Since as you know now, mouser is preparing an update !!!  :D

historys bug
======================
when you select a previous search through the historys command, a space is appended to it
so basically if your last search is : search keyword
then if you select your last search through the historys command you'll get
search keyword{space}


showmemo bug
======================
bug using the showmemo command :
only the first line break (\n) works ... after that it shows "\n" ...


folder with a dash bug
======================
F&R fails to list files in a folder with a dash in its name (b142)
reported by jzippo


clipboard bugs
======================
  • $$c is empty if the clipboard content is too big (limit should be removed)
  • the "restartsearch $$c" command crashes FARR when the clipboard content is too big (above 1024  characters ?)


search box bug
======================
since the 2.00.130 release and the new result display updating, there is no more flickering but the search box is not responsive as before...
it really really should be an option

in anycase the search box should feel completely free

for example when i use one of my (dosearch) alias which searches music on my network drive, it takes literally 10 seconds before i see the search terms i typed after the alias trigger... let's say my alias is triggered by music, if a type "music madonna"
i see music, then FARR stops for 10 seconds (i know it's working but it feels like it just crashed) then madonna comes up then the search ends (an other 10 seconds later)

i really (only?) notice it when using dosearch aliases


action trick bug
======================
in my opinion this is the most important bug
https://www.donation...dex.php?topic=9161.0

the +action trick TOO clever
i think the +action trick is trying to be clever and detect that there is only one result, and so it should show you text about the action.  that's normally what you want, so that you can see what action will be applied to what file.
as i suggested the +action trick when used with dosearch command is way to clever it shoud just be fired when asked !

edit : an other problem with the action trick (when used in a dosearch)
is that if you want to use the shell contextual menu or simply the contextual menu on your single result (the action trick is triggered when only one result is found...) you CANNOT
it will open the contextual menu or shell menu of the action file
VERY BAD  ;D


$$1, problem when passing "C:\" bug
======================
https://www.donation...dex.php?topic=9222.0


keyword with capital bug
======================
MAJOR bug
https://www.donation...dex.php?topic=8338.0
keywords with capital does not work at all


same name bug ?
======================
when using the same name for a folder keyword and an alias
of a folder keyword and a action keyword
FARR does not work well
solution is to prefix keyword with : folder for folder keywords
action for action keywords


=================
i surely forgot some, if you know of other outstanding bugs please report them in this thread

Cheers, Nitrix
« Last Edit: October 16, 2007, 10:05 AM by nitrix-ud »

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,896
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #1 on: October 15, 2007, 01:10 PM »
Very helpful to have this summary, thank you.

nitrix-ud

  • Charter Member
  • Joined in 2005
  • ***
  • default avatar
  • Posts: 560
    • View Profile
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #2 on: October 24, 2007, 03:29 PM »
@mouser or josh

i think the clipboard bugs are still outstanding
could you please add it to the official bug report thread

Thanks, Nitrix

nitrix-ud

  • Charter Member
  • Joined in 2005
  • ***
  • default avatar
  • Posts: 560
    • View Profile
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #3 on: October 26, 2007, 09:50 AM »
considering the same name bug which status is : not issue?

i kind of agree this is not really an issue BUT it can/will cause problems to some

it should be said somewhere that using the same name for a folder keyword and an action keyword can confuse FARR
or even better, FARR should warn the user when he specify the same name (but i imagine it's not that easy to check since the "action trick modifier" is the actual name of an alias)

Nitrix

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,896
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #4 on: October 26, 2007, 12:16 PM »
warning the user for duplicate alias names is not a bad idea, i'll put that on my todo list.

As you saw, Josh took this idea for a summary bug list and really ran with it in a nice way so that now all of my major programs has such a list which can be thought of as a kind of bugtracker (https://www.donation...ex.php?topic=10533.0).

gogogadgetscott

  • Supporting Member
  • Joined in 2007
  • **
  • Posts: 23
  • Mechanical engineer who has inexplicable knowledge
    • View Profile
    • GoGoGadgetScott's Site
    • Read more about this member.
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #5 on: February 13, 2008, 08:50 AM »
clipboard bug
======================
When using %clipboard% in an alias command, as per docs, the var is not replaced with the contents of the clipboard.
https://www.donation...clipboard_tricks.htm

Is there is difference between $$c and %clipboard%?

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,896
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: [bugs report] here is a list of outstanding bugs
« Reply #6 on: February 13, 2008, 02:10 PM »
there is actually a difference.
%clipboard% should ALWAYS be replaced with clipboard text (blank if clipboard text is blank).

$$c can be used to mean $$1 unless its blank, and clipboard text if it is blank.
for example from the help file:
  • So an alias might match on text gsearch(.*)
  • with result: gsearch $$c | http://www.google.com?query=$$c
  • When user types "gsearch hello" it will open a search to hello
  • When user types "gsearch" it will open a search to clipboard text

so $$c is used where you might normally put $$1

ps.
you can also manually tell farr to use your clipboard text in a search by typing $c

so if you have an alias like "define (.*)" which uses $$1 in its search, you could TYPE in the search box "define $c" and it will be as if you typed ("define CLIPBOARD_TEXT_HERE").
« Last Edit: February 13, 2008, 02:13 PM by mouser »