From: "Colin S. Miller" <no-spam-thank-you@csmiller.demon.co.uk>
Subject: Re: current directory
Date: Mon, 23 Oct 2006 19:33:09 +0100 [thread overview]
Message-ID: <453d0ae6$0$49201$14726298@news.sunsite.dk> (raw)
In-Reply-To: <mailman.166.1161624291.27805.help-gnu-emacs@gnu.org>
vb wrote:
> On Saturday 21 October 2006 11:38, don provan wrote:
>
> no, it would not be insane at all. All other editors but emacs I am used to
> maintain a notion of "current directory" and allow the user to change this
> current directory explicitly. The fact that emacs doesn't even have an
> infrastructure for that just shows how off mark its approach is.
>
I find it interesting to note that in MS VC 6,
File/Open defaulted to the last directory you open a file from,
and MS VC .NET now defaults to the directory of the current file.
>
> As I said, look around, check out Crisp for instance, you would be surprised:
> no long keystrokes, much wider use of keys (say astersk on the numeric keypad
> and on the main keyboard are naturally assigned to different key codes _
> still have to find the way to achieve this with emacs, and I've tried!). You
> can write macros in object oriented c-like language, not in this weird lisp
> which is a remnant of computing stone age (I know, I know that it is still
> used to teach students).
(global-set-key 'kp-multiply 'switch-to-buffer)
C-h k * indicates the internal name for keystrokes
BTW,
in answer to your original question,
you could make the call-progress run
"cd /a/b/c && ./myScript.sh"
It is possible for emacs to record its starting directory,
and add the cd for you.
HTH,
Colin S. Miller
--
Replace the obvious in my email address with the first three letters of the hostname to reply.
next prev parent reply other threads:[~2006-10-23 18:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.83.1161235004.2130.help-gnu-emacs@gnu.org>
2006-10-19 16:01 ` current directory Fang lun gang
2006-10-19 16:52 ` vb
2006-10-20 6:22 ` Eli Zaretskii
[not found] ` <mailman.100.1161276782.2130.help-gnu-emacs@gnu.org>
2006-10-19 19:22 ` rgb
2006-10-19 21:00 ` vb
2006-10-21 18:38 ` don provan
2006-10-23 17:24 ` vb
2006-10-23 19:17 ` John Sullivan
2006-10-23 19:57 ` Eli Zaretskii
2006-10-23 20:36 ` vb
2006-10-23 21:47 ` Dieter Wilhelm
2006-10-24 4:26 ` Eli Zaretskii
2006-10-24 5:24 ` Dieter Wilhelm
[not found] ` <mailman.178.1161635783.27805.help-gnu-emacs@gnu.org>
2006-10-23 21:52 ` Maarten Bergvelt
2006-10-23 20:32 ` Kevin Rodgers
2006-10-23 20:59 ` vb
[not found] ` <mailman.166.1161624291.27805.help-gnu-emacs@gnu.org>
2006-10-23 17:48 ` David Kastrup
2006-10-23 20:03 ` Eli Zaretskii
2006-10-23 18:33 ` Colin S. Miller [this message]
2006-10-23 18:58 ` vb
[not found] ` <mailman.169.1161629903.27805.help-gnu-emacs@gnu.org>
2006-10-23 19:46 ` Peter Boettcher
[not found] <mailman.74.1161208352.2130.help-gnu-emacs@gnu.org>
2006-10-20 16:46 ` Sam Peterson
2006-10-19 5:16 help-gnu-emacs
2006-10-20 5:49 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 21:52 help-gnu-emacs
2006-10-18 22:32 ` Peter Dyballa
2006-10-18 23:12 ` vb
2006-10-19 4:25 ` Eli Zaretskii
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='453d0ae6$0$49201$14726298@news.sunsite.dk' \
--to=no-spam-thank-you@csmiller.demon.co.uk \
/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).