New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path style issue with eblook and Cygwin #12

Closed
yasuhirokimura opened this Issue Sep 17, 2013 · 6 comments

Comments

Projects
None yet
2 participants
@yasuhirokimura
Contributor

yasuhirokimura commented Sep 17, 2013

On Windows I build eblook from source code with Cygwin and use it as backend of ndeb agent. Generally speaking, programs build on Cygwin accept both Windows style path(c:/foo/bar/baz.txt) and Unix style one(/cygdrive/c/foo/bar/baz.txt). However when build on Cygwin eblook only accepts later one. So local dictionary path must be
specified as below:

eblook /cygdrive/c/path/to/dictionary/dict_name

But if I put following setting in ~/.emacs.d/lookup/init.el,

(setq lookup-search-agents
      '(
        (ndeb "/cygdrive/c/path/to/dictionary/dict_name")
        )
      )

and start lookup then I get following error message in minibuffer:

error in process filter: Invalid book directory: c:/cygdrive/c/path/to/dictionary/dict_name

It seems dictionary path is handled with Windows style and drive letter is added according to current working directory. But as described above, Unix type path must be passed to eblook. So are there any ways to solve this issue?

@ikazuhiro

This comment has been minimized.

Show comment
Hide comment
@ikazuhiro

ikazuhiro Sep 17, 2013

Member

Please use native Windows binary of eblook for NTEmacs. As you described, Cygwin's eblook does not support DOS style path name. That is mainly due to the limitation of EB Library, which has own path name handling routines. And I think it requires very dirty kludge to let NTEmacs talk with Cygwin's eblook with no problem, especially in multimedia data handling.
If eblook's binary has any problem, please let me know.

Member

ikazuhiro commented Sep 17, 2013

Please use native Windows binary of eblook for NTEmacs. As you described, Cygwin's eblook does not support DOS style path name. That is mainly due to the limitation of EB Library, which has own path name handling routines. And I think it requires very dirty kludge to let NTEmacs talk with Cygwin's eblook with no problem, especially in multimedia data handling.
If eblook's binary has any problem, please let me know.

@yasuhirokimura

This comment has been minimized.

Show comment
Hide comment
@yasuhirokimura

yasuhirokimura Sep 18, 2013

Contributor

I switched from Cygwin eblook to eblook-1.6.1+media-20110801-ebu-4.4.3-20110801.exe and lookup worked fine with local dictionary, but not with ebnetd.

(setq lookup-search-agents
      '(
        (ndeb "ebnet://ebnetd.example.org:22010/dic_name")
        )
      )

With ~/.emacs.d/lokkup/init.dl above, lookup failed to start up with following error message in minibuffer:

error in process filter: Invalid book directory: ebnet://ebnetd.example.org:22010/dic_name

This time, different from issue #9, URL of ebnet server seemed to be passed correctly. And there is another difference. On Windows command prompt,

C:\Users\username> eblook ebnet://ebnetd.example.org:22010/dic_name

started up without any errors. And moreover, all of selecting dictionary, searching word, displaying result, etc. worked fine. So I was unable to guess what is wrong in this case.

Contributor

yasuhirokimura commented Sep 18, 2013

I switched from Cygwin eblook to eblook-1.6.1+media-20110801-ebu-4.4.3-20110801.exe and lookup worked fine with local dictionary, but not with ebnetd.

(setq lookup-search-agents
      '(
        (ndeb "ebnet://ebnetd.example.org:22010/dic_name")
        )
      )

With ~/.emacs.d/lokkup/init.dl above, lookup failed to start up with following error message in minibuffer:

error in process filter: Invalid book directory: ebnet://ebnetd.example.org:22010/dic_name

This time, different from issue #9, URL of ebnet server seemed to be passed correctly. And there is another difference. On Windows command prompt,

C:\Users\username> eblook ebnet://ebnetd.example.org:22010/dic_name

started up without any errors. And moreover, all of selecting dictionary, searching word, displaying result, etc. worked fine. So I was unable to guess what is wrong in this case.

@ikazuhiro

This comment has been minimized.

Show comment
Hide comment
@ikazuhiro

ikazuhiro Sep 19, 2013

Member

Confirmed, that is eblook's bug. Please try fixed version.

Member

ikazuhiro commented Sep 19, 2013

Confirmed, that is eblook's bug. Please try fixed version.

@yasuhirokimura

This comment has been minimized.

Show comment
Hide comment
@yasuhirokimura

yasuhirokimura Sep 19, 2013

Contributor

Please try fixed version.

Using this version lookup works fine with both local dictionaryies and ebnetd.

BTW binary of fixed version requires zlib1.dll. So if you are going to replace eblook-1.6.1+media-20110801-ebu-4.4.3-20110801.exe , would you please provide eblook binary that zlib is statically linked and that can be used as is?

Best Regards.

Contributor

yasuhirokimura commented Sep 19, 2013

Please try fixed version.

Using this version lookup works fine with both local dictionaryies and ebnetd.

BTW binary of fixed version requires zlib1.dll. So if you are going to replace eblook-1.6.1+media-20110801-ebu-4.4.3-20110801.exe , would you please provide eblook binary that zlib is statically linked and that can be used as is?

Best Regards.

@ikazuhiro

This comment has been minimized.

Show comment
Hide comment
@ikazuhiro

ikazuhiro Sep 20, 2013

Member

Oops, I updated eblook and binaries. I checked binaries were linked with zlib and EB Library statically. Please test it.

Member

ikazuhiro commented Sep 20, 2013

Oops, I updated eblook and binaries. I checked binaries were linked with zlib and EB Library statically. Please test it.

@yasuhirokimura

This comment has been minimized.

Show comment
Hide comment
@yasuhirokimura

yasuhirokimura Sep 20, 2013

Contributor

I confirmed that eblook-1.6.1+media-20130919-ebu-4.4.3-20130920.exe doesn't require any additional DLL's and that it works fine with lookup.

Thank you for rapid response.

Contributor

yasuhirokimura commented Sep 20, 2013

I confirmed that eblook-1.6.1+media-20130919-ebu-4.4.3-20130920.exe doesn't require any additional DLL's and that it works fine with lookup.

Thank you for rapid response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment