unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: g-client: character coding problem
Date: Mon, 14 May 2007 17:45:37 +1000	[thread overview]
Message-ID: <87zm47g866.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 87d514l9dm.fsf@gmail.com

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.

BTW, can someone tell me what emacs 23 is? I'm running from CVS and it reports
the version as emacs 22. I've seen a number of references to emacs 23, which
I've not heard of and didn't think existed (given that I would expect the CVS
to be the latest version).

Tim

Tim
-- 
tcross (at) rapttech dot com dot au

  reply	other threads:[~2007-05-14  7:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 14:55 g-client: character coding problem Joseph Fahey
2007-05-13 15:33 ` Hadron
2007-05-13 15:43   ` Hadron
2007-05-13 17:55     ` Joseph Fahey
2007-05-13 21:08       ` Hadron
2007-05-14  7:45         ` Tim X [this message]
2007-05-14  9:36           ` Hadron
2007-05-17  8:49             ` Tim X
2007-05-14  9:39           ` Hadron
2007-05-14 10:16           ` Peter Dyballa
     [not found]           ` <mailman.631.1179138267.32220.help-gnu-emacs@gnu.org>
2007-05-14 10:31             ` Hadron
2007-05-14 12:12               ` Peter Dyballa
2007-05-14  7:28 ` Enchanter
2007-05-14  7:49   ` Tim X

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zm47g866.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).