all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
Subject: Re: Time to throw away my LOVE - Emacs ?
Date: Tue, 8 Jun 2004 17:06:38 +0000	[thread overview]
Message-ID: <umr4ac.fu.ln@acm.acm> (raw)
In-Reply-To: 40c5da09$1@news.012.net.il

Barak Zalstein <no_spam@please.not> wrote on Tue, 8 Jun 2004 18:22:51 +0300:
>> Are you suggesting that other programming paradigms (anything "visual")
>> are a barrier to enhanced productivity?  If so, I agree with you.

> Not really.

> If you can't interact with the other programming tool from Emacs, because of
> a closed non-text data representation, or a format which is not manipulated
> well by a text editor (icons, bitmaps etc.), or simply a certain development
> tool feature which is reachable only through a GUI menu,

Sorry, I can scarcely follow what you're saying.  What do you mean by
"interact with the other programming tool from Emacs"?  What does
"interact" mean here?  Quite simply, Emacs doesn't deal with closed
non-text formats.  If you have, e.g., a file.pdf, you use a different
program.  For icons and bitmaps, you'll be using an icon/bitmap program.
The interaction with Emacs comes from specifying the filename to a
program.

Can you give an example of what you mean by a "tool feature ...
reachable only through a GUI menu", which you might want to call from
Emacs?

> .... switching back and forth to Emacs or trying to figure out how not
> to drop Emacs from the development cycle _is_ the barrier to enhanced
> productivity.

I think you've got a particular scenario in mind here.  Would you like to
spell it out in detail?  TIA.

> I don't think that this is seeing things from the wrong angle, when
> merely keeping up with changing standards and interfaces of default
> common tools demands continuous and active effort from an Emacs user .

Emacs is a default common tool.  As for others, keeping up with them
demands effort whether one's an Emacs user or not.

> Barak.

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").

  reply	other threads:[~2004-06-08 17:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7e4qpod2db.fsf@ada2.unipv.it>
     [not found] ` <zn7g86jv.fsf_-_@ipanel.cn>
     [not found]   ` <un03f1k7n.fsf@standardandpoors.com>
     [not found]     ` <40c49fc7$1@news.012.net.il>
     [not found]       ` <uise318fg.fsf@standardandpoors.com>
     [not found]         ` <87ise3t36i.fsf@tc-1-100.kawasaki.gol.ne.jp>
2004-06-08  7:45           ` Time to throw away my LOVE - Emacs ? Alan Mackenzie
2004-06-08  9:08             ` David Kastrup
2004-06-08 10:56               ` Alan Mackenzie
2004-06-08 13:20                 ` Barak Zalstein
2004-06-08 13:57                   ` Alan Mackenzie
2004-06-08 15:22                     ` Barak Zalstein
2004-06-08 17:06                       ` Alan Mackenzie [this message]
2004-06-09  8:01                         ` Barak Zalstein
2004-06-09  7:53                           ` Alan Mackenzie
2004-06-10  4:57                             ` Barak Zalstein
2004-06-09  9:59                           ` Barak Zalstein
2004-06-08 22:30                       ` Miles Bader
2004-06-08 13:54           ` Galen Boyer
2004-06-11 19:31             ` Marco Parrone

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=umr4ac.fu.ln@acm.acm \
    --to=acm@muc.de \
    /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.