From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gdb call with core
Date: Mon, 15 May 2006 23:37:41 +0300 [thread overview]
Message-ID: <uzmhj2fe2.fsf@gnu.org> (raw)
In-Reply-To: <q5gwtcnstlg.fsf@sfsw51.de.lucent.com> (message from Klaus Zeitler on Mon, 15 May 2006 08:14:03 +0200)
> Cc: emacs-devel@gnu.org
> From: Klaus Zeitler <kzeitler@lucent.com>
> Date: Mon, 15 May 2006 08:14:03 +0200
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> Eli>
> Eli> I can see why this is reasonable. Why do you think it's bad?
>
> I hope I didn't say "bad", I just wanted to point out that it's sometimes
> a bit inconvenient.
``Bad'' as in ``inconvenient''.
> Besides the current behavior is also sometimes a bit confusing. For example
> last Friday I tried to look at an emacs core (in my current directory where
> emacs had just written the core) with "gdb path-to-emacs/emacs core". After a
> short glance I decided to take a closer look, which for me means I need emacs
> with gud, so I started emacs in this directory and tried the same command that
> I had just executed in the shell and now emacs couldn't find the core.
It takes time to get used to the notion that in Emacs, you are always
in the directory of the current buffer. When you do get used to it,
things like that really make sense to you.
In other words, the fact that you invoked Emacs from some directory
says nothing at all about what will be the value of PWD for some
arbitrary Emacs command.
next prev parent reply other threads:[~2006-05-15 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 9:57 gdb call with core Klaus Zeitler
2006-05-12 11:25 ` Eli Zaretskii
2006-05-12 11:50 ` Klaus Zeitler
2006-05-12 13:36 ` Eli Zaretskii
2006-05-12 14:26 ` Stefan Monnier
2006-05-13 6:59 ` Nick Roberts
2006-05-13 16:25 ` Stefan Monnier
2006-05-13 21:45 ` Nick Roberts
2006-05-15 6:14 ` Klaus Zeitler
2006-05-15 20:37 ` Eli Zaretskii [this message]
[not found] ` <17509.46549.5651.16043@localhost.localdomain>
2006-05-12 12:03 ` Klaus Zeitler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uzmhj2fe2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.