Re: g-client: character coding problem

[Hadron]

Tim X <timx@nospam.dev.null> writes:

> Hadron <hadronquark@gmail.com> writes:
>
>> Joseph Fahey <fahey@fabula.org> writes:
>>
>>>>>>>> "h" == Hadron  <hadronquark@gmail.com> writes:
>>>
>>>     h> Hadron <hadronquark@gmail.com> writes:
>>>     >> Joseph Fahey <fahey@fabula.org> writes:
>>>     >> 
>>>     >>> I am trying to use T. V. Ramah's g-client interface to the
>>>     >>> Google API, in particular as an interface to Blogger.
>>>     >>> 
>>>     >>> 
>>> http://emacspeak.blogspot.com/2007/03/emacs-client-for-google-services.html#cooliris
>>>     >> 
>>>     >> With emacs 23 I get this error
>>>     >> 
>>>     >> ,---- | Debugger entered--Lisp error: (file-error "Cannot open
>>>     >> load file" "g-cus-load") | load("g-cus-load") |
>>>     >> load-library("g-cus-load") |
>>>     >> byte-code("ÀÁÂÃÄÅ%.ÆÇ!.ÆÈ!.ÉÊË\".ÌÁ!."
>>>     >> [custom-declare-group g nil "Google Client" :group applications
>>>     >> load-library "g-loaddefs" "g-cus-load" add-hook
>>>     >> calendar-mode-hook gcal-emacs-calendar-setup provide] 6) |
>>>     >> load("g") | load-library("g") | eval((load-library "g")) |
>>>     >> eval-last-sexp-1(nil) | eval-last-sexp(nil) |
>>>     >> call-interactively(eval-last-sexp) `----
>>>     >> 
>>>     >> Any ideas?
>>>
>>>     h> ok, just commenting out the line in g.el which loads g-cus-load
>>>     h> gets it working, but what lisp would load the file only if it
>>>     h> exists?
>>>
>>> That problem has been fixed in the most recent svn version. When I
>>> first installed g-client, the fix was to add your own g-cus-load.el
>>> file that would be empty except for "(provide 'g-cus-load)".
>>>
>>> Joe
>>
>> Why would anyone leave the main release with an error in it that
>> literally stops emacs loading properly? Strange.
>
> Not that strange if you realise g-client has been developed as part of
> emacspeak and if you use it with emacspeak, that file is not empty.

No. It is that strange. The download I took *is* a standalone
package. You have said "why it is broken" rather than justify it not
being corrected. I'm not necessarily criticising, just pointing out that
the effort to replace the package file is very small and would enable a
few people to "just install and use it" rather than have a totally broken
emacs.

It's a neat little package btw!