Messages - donw [ switch to compact view ]

Pages: [1] 2 3 4next
1
DcUpdater / Re: DcUpdater fails to check for updates
« on: May 09, 2020, 02:04 PM »
Happening to me as well. The text is "get version failed"

2
LaunchBar Commander / Re: 1.149.01 and 1.149.04 both hanging
« on: January 19, 2017, 10:21 PM »
My problem is fixed. As I determined when I updated an old Dell laptop, the install of 1.149.04 worked fine with the old files. It was only when I synced the files from my main desktop that the hanging started. I updated my desktop to 1.149.04, synced the new files and reinstalled 1.149.04 on the laptops and all is working fine.

I encourage you to make 1.149.04 an official release, available through DcUpdater.

Thanks again for a great product. FARR also proved really useful when I was having these problems.

3
LaunchBar Commander / Re: 1.149.01 and 1.149.04 both hanging
« on: January 17, 2017, 09:48 PM »
By "hanging" I mean that LaunchBarCommander.exe is keeping one CPU core pinned at maximum. I've let it go for about 1 hour without any change.

There are some network drives. None of them are new as my setup is pretty stable.

Let me know if you want me to try the debug version.

4
LaunchBar Commander / 1.149.01 and 1.149.04 both hanging
« on: January 16, 2017, 03:57 PM »
I'm running Win Pro x64 on all machines.
I first installed 1.149.01 on my HP desktop and it worked fine.
I then installed it on a Lenovo W520 laptop and it hung with the CPU busy. After a number of uninstalls, reinstalls and general machine cleanup it started working again.
I then installed it on a Lenovo W530 laptop and it hung with the CPU busy. I then uninstalled and tried 1.149.04. It still hangs.
All my settings files are copied from the HP desktop master copy. I've been doing this for years without any problems. Let me know if you need any more info to fix this.

5
After watching some more of the FARR videos (thanks mouser), I have come up with a partial solution to finding aliases without having to type +alias at the end of a search. I turned off the Required Alias Prefix and defined the following alias:

1000>>>alias search>->dosearch $$1 +alias>+>^a (.*)$

This alias allows me to see all the aliases starting with "b" by typing "a b", which is one character longer than typing "`b" when I has the Required Alias Prefix set. It is not perfect as it only lists fixed aliases and doesn't list regular expression aliases. It also inserts "+alias" into regular expression aliases like fc, which could be coded to ignore "+alias" but typically haven't been made that fancy.

To summarize: I have an acceptable workaround. It would be nice if the behavior of FARR with the Required Alias Prefix was smarter as it really isn't very usable right now. This problem won't stop me from using FARR as I think it is a very flexible and powerful product.

Pages: [1] 2 3 4next
Go to full version