unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Michel Salim" <michel.salim@gmail.com>
Cc: bug@octave.org, bug-gnu-emacs@gnu.org,
	"John W. Eaton" <jwe@bevo.che.wisc.edu>
Subject: Re: CDPATH problem reappears when using octave-2.9.9 from Emacs 23
Date: Thu, 26 Oct 2006 01:33:10 -0400	[thread overview]
Message-ID: <883cfe6d0610252233p502ab750ge17ba1b13ff170b3@mail.gmail.com> (raw)
In-Reply-To: <E1Gbs6K-00009V-1h@fencepost.gnu.org>

On 10/23/06, Richard Stallman <rms@gnu.org> wrote:
>     In any case, I looked at the Emacs lisp files that are distributed
>     with the pre-release of Emacs that I am using and it appears that this
>     message could come from the cd function.
>
> It looks that way.
>
> Michel, how about if you do  M-x toggle-debug-on-error,
> and see how cd is actually being called and from where and why?
>
The last function called before the error was
inferior-octave-resync-dirs(), called by inferior-octave-startup(),
called by run-octave(nil). The directory that's not found via CDPATH
is whatever the current directory is when emacs was invoked.

The bizarre thing is:
1. This does not get triggered by octave 2.9.8
2. adding that directory to CDPATH does not change the result
3. I've tried using the emacs mode shipped with Octave by adding them
to the load-path, and get the same error. So it's probably not caused
by the difference between the two modes.

The curious thing is, the last time a CDPATH problem was reported in
relation to Octave, the solution was precisely to add the call to
inferior-octave-resync-dirs() ...

http://velveeta.che.wisc.edu/octave/lists/archive//help-octave.2005/msg03088.html

Thanks for looking into this - I could go back to Emacs 21.4, but CVS
23 looks so much more polished.

-- 
Michel Salim
http://salimma.livejournal.com

  reply	other threads:[~2006-10-26  5:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 21:09 CDPATH problem reappears when using octave-2.9.9 from Emacs 23 Michel Salim
2006-10-21 14:06 ` John W. Eaton
2006-10-23  5:11   ` Richard Stallman
2006-10-26  5:33     ` Michel Salim [this message]
2006-10-26 10:11       ` Richard Stallman
2006-10-26 12:58         ` Michel Salim
2006-10-26 13:54           ` John W. Eaton
2006-10-26 23:59             ` Michel Salim

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=883cfe6d0610252233p502ab750ge17ba1b13ff170b3@mail.gmail.com \
    --to=michel.salim@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug@octave.org \
    --cc=jwe@bevo.che.wisc.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).