fzxs8 / chmsee

Automatically exported from code.google.com/p/chmsee
GNU General Public License v2.0
0 stars 0 forks source link

chmsee does not resolve relative path from command line parameters #155

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. cd into a directory with foo.chm in it.
2. xulrunner /usr/share/chmsee/application.ini foo.chm

What is the expected output? What do you see instead?
chmsee should open the file foo.chm. but it actually opens a default page 
instead of the file.

What version of the product are you using? On what operating system?
2.0. archlinux

Please provide any additional information below.
if we provide chmsee with full path, it opens the file correctly.

Original issue reported on code.google.com by augu...@gmail.com on 29 Jan 2013 at 2:14

GoogleCodeExporter commented 9 years ago
I can't repeat the same issue on my arch64 box.

Following is my testing procedure:

$ xulrunner --version
Mozilla XULRunner 18.0 - 20130108152131
$ uname -a
Linux HOSTNAME="arch64" 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 
2013 x86_64 GNU/Linux

$ rm -rf ~/.chmsee
$ cd ~/tmp
$ xulrunner ~/projects/chmsee/application.ini apue2.chm

chmsee will open apue2.chm correctly.

You can clear .chmsee cache folder and try again.

If the problem is still there, please change CsDebug from false to true on 
chrome/content/utils.js line 221:

const CsDebug = true;

After save utils.js, clear ~/.chmsee, launch chmsee and paste the output here.

Original comment by jungl...@gmail.com on 30 Jan 2013 at 3:30

GoogleCodeExporter commented 9 years ago
Issue 156 has been merged into this issue.

Original comment by jungl...@gmail.com on 30 Jan 2013 at 3:30

GoogleCodeExporter commented 9 years ago
using your method, i can correctly open .chm files from command line.

this may be a packaging bug. anyway, removing the whole ~/.chmsee folder seems 
to be helpful.

Original comment by augu...@gmail.com on 30 Jan 2013 at 4:36