all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Dan Espen" <daneNO@more.mk.spamtelcordia.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: What I'm missing when using M-x shell
Date: Sat, 13 Sep 2008 18:43:04 +0200	[thread overview]
Message-ID: <38b2ab8a0809130943s58aed564seee22a18032c439a@mail.gmail.com> (raw)
In-Reply-To: <icabecuk6g.fsf@verizon.net>

On Sat, Sep 13, 2008 at 5:42 PM, Dan Espen
<daneNO@more.mk.spamtelcordia.com> wrote:
> "Francis Moreau" <francis.moro@gmail.com> writes:
>
>> [ please CC me when replying to me ]
>>
>> On Fri, Sep 12, 2008 at 7:34 PM, Dan Espen
>> <daneNO@more.mk.spamtelcordia.com> wrote:
>>> Compiles are M-x compile, greps are M-x grep,
>>> ls is dired, email is MH-E.
>>
>> But what would you suggest as replacement for:
>>
>> $ make && gdb || mail -s "Compilation failed" home
>
> First, the make is always run as M-x compile.
>
> In my case, the most likely outcome from M-x compile is
> that I'll be correcting syntax errors.  Since I've run
> M-x compile, M-x next-error becomes really useful.
>
> So, no make from the command line for me.
>
> I'm got a big fan of running under gdb.
> If I did want to run under gdb a lot, I'd probably figure out
> Emacs gdb.
>
> Typically my make target is not just a compile but a compile
> and test and check results.  No need to send myself
> an email since the M-x compile clearly shows whether the
> compile/test worked.
>

That was just a (silly) example where scripting can be powerful and
can't be replace by some M-x <cmd> or whatever...

-- 
Francis




  reply	other threads:[~2008-09-13 16:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.19125.1221236437.18990.help-gnu-emacs@gnu.org>
2008-09-12 17:34 ` What I'm missing when using M-x shell Dan Espen
2008-09-13  8:27   ` Francis Moreau
2008-09-15  7:32     ` Jonathan Groll
2008-09-15  8:42       ` Francis Moreau
2008-09-15  9:05         ` Francis Moreau
     [not found]   ` <mailman.19169.1221294471.18990.help-gnu-emacs@gnu.org>
2008-09-13 15:42     ` Dan Espen
2008-09-13 16:43       ` Francis Moreau [this message]
2008-09-13 17:32         ` Thierry Volpiatto
2008-09-13 19:14           ` Francis Moreau
2008-09-13 19:50             ` Thierry Volpiatto
2008-09-14  4:02     ` Tim X
2008-09-12 17:59 ` Oleksandr Gavenko
2008-09-13  8:29   ` Francis Moreau
     [not found]   ` <mailman.19170.1221294576.18990.help-gnu-emacs@gnu.org>
2008-09-15 18:32     ` Oleksandr Gavenko
2008-09-13  6:10 ` rustom
2008-09-13  8:36   ` Francis Moreau
2008-09-13  8:08 ` Livin Stephen
2008-09-13  9:00   ` Francis Moreau
2008-09-13 11:21     ` Livin Stephen Sharma
2008-09-13 14:27       ` Francis Moreau
2008-09-13 12:22   ` David Hansen
2008-09-14  2:20   ` Tim X
2008-09-15  7:56     ` Livin Stephen
2008-09-15  8:49       ` Francis Moreau
2008-09-13 22:43 ` Chris F.A. Johnson
2008-09-14 18:30   ` Francis Moreau
2008-09-14 18:40     ` Thierry Volpiatto
     [not found]     ` <mailman.19222.1221417839.18990.help-gnu-emacs@gnu.org>
2008-09-14 18:55       ` Barry Margolin
2008-09-14 20:28         ` Francis Moreau
2008-09-14 20:41           ` Francis Moreau
     [not found]   ` <mailman.19221.1221417026.18990.help-gnu-emacs@gnu.org>
2008-09-14 18:33     ` Chris F.A. Johnson
2008-09-14 18:50       ` Drew Adams
2008-09-14 20:01       ` Francis Moreau
2008-09-15 10:26         ` Bernardo Bacic
     [not found]       ` <mailman.19228.1221422522.18990.help-gnu-emacs@gnu.org>
2008-09-14 20:27         ` Chris F.A. Johnson
2008-09-15  6:32           ` Francis Moreau
2008-09-15 10:35             ` Francis Moreau
2008-09-15 11:38             ` Thierry Volpiatto
2008-09-15 12:10               ` Francis Moreau
2008-09-15 13:00                 ` Thierry Volpiatto
2008-09-15 13:13                   ` Francis Moreau
2008-09-12 16:20 Francis Moreau

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=38b2ab8a0809130943s58aed564seee22a18032c439a@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=daneNO@more.mk.spamtelcordia.com \
    --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.
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.