unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: arthur miller <arthur.miller@live.com>
To: "rms@gnu.org" <rms@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: "Adobe Brackets like" editing in emacs
Date: Wed, 19 Mar 2014 10:01:04 +0100	[thread overview]
Message-ID: <DUB111-W2666850D0577A6531691EB967F0@phx.gbl> (raw)
In-Reply-To: <E1WQ7gW-00061h-BO@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]

Here is a picture of how it looks like: 

http://dev.brackets.io/preso/intro/assets/features/brackets-quick-edit-js.PNG

I don't know if they have trademark for "quick edit" :-), but since they actually develop Brackets as open source, I hope they keep their terms open source as well. I also hope they didn't patented :).

As Stephan wrote, it could be seen as analogy to a link, but instead of visiting a link the text is pulled into the current buffer under the cursor. I used "intellisense" analogy because I was thinking of context awareness indeed, not of the looks. But link analaogy is indeed better.

I think difference of editing in new window, versus pulling piece of buffer into same window, makeing seemles illusion of editing same file, is workflow 
enhacement. If I may take freedom to allude on another such workflow enhacement, I would compare it to difference between Vi and Emacs, and "direct  text" editing as in Emacs compared to "command mode" editing as in Vi. I think it is such kind of a difference. 


> Date: Wed, 19 Mar 2014 00:00:56 -0400
> From: rms@gnu.org
> To: emacs-devel@gnu.org
> CC: emacs-devel@gnu.org
> Subject: Re: "Adobe Brackets like" editing in emacs
> 
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 
>     A quick peek+edit in a #include in C, or "use My::Module" in Perl (where
>     you can say `perldoc -l My::Module' to find the module file), etc. would
>     be handy.
> 
> We already have such features, but they display the other file in
> another buffer.	  Why is it useful to put them in one buffer?
> 
> What does it look like, to have multiple files in one buffer?
> 
> -- 
> Dr Richard Stallman
> President, Free Software Foundation
> 51 Franklin St
> Boston MA 02110
> USA
> www.fsf.org  www.gnu.org
> Skype: No way! That's nonfree (freedom-denying) software.
>   Use Ekiga or an ordinary phone call.
> 
> 
 		 	   		  

[-- Attachment #2: Type: text/html, Size: 2500 bytes --]

  parent reply	other threads:[~2014-03-19  9:01 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 13:29 "Adobe Brackets like" editing in emacs arthur miller
2014-03-18 19:01 ` Richard Stallman
2014-03-18 19:24   ` arthur miller
2014-03-19  4:18     ` Stephen J. Turnbull
2014-03-19 14:01       ` Ivan Andrus
2014-03-19 15:03         ` Lennart Borgman
2014-03-19 15:16           ` arthur miller
2014-03-19 15:24             ` Lennart Borgman
2014-03-19 15:31           ` Ivan Andrus
2014-03-19 15:40             ` Lennart Borgman
2014-03-19 16:20               ` Stephen J. Turnbull
2014-03-19 16:37                 ` Lennart Borgman
2014-03-19 16:42                   ` Lennart Borgman
2014-03-19 18:18               ` Richard Stallman
2014-03-18 19:37   ` arthur miller
2014-03-18 21:29     ` Alan Schmitt
     [not found]       ` <DUB111-W4468B0D4051AE6F0B217B2967C0@phx.gbl>
2014-03-18 21:42         ` arthur miller
2014-03-19 16:01           ` Tom
2014-03-19 18:18             ` Richard Stallman
2014-03-20 11:04               ` Phillip Lord
2014-03-20 11:58                 ` arthur miller
2014-03-20 18:57                   ` Richard Stallman
2014-03-21 11:36                     ` Phillip Lord
2014-03-21 16:58                       ` chad
2014-03-21 18:58                         ` Richard Stallman
2014-03-20 12:50                 ` Stefan
2014-03-20 14:40                   ` Phillip Lord
2014-03-20 13:17                 ` Ted Zlatanov
2014-03-20 16:00                   ` Phillip Lord
2014-03-18 20:36   ` Ted Zlatanov
2014-03-19  4:00     ` Richard Stallman
2014-03-19  4:09       ` Vibhav Pant
2014-03-19  8:06         ` Tom
2014-03-19  9:15         ` Stephen J. Turnbull
2014-03-19 16:17           ` Eli Zaretskii
2014-03-19 16:01         ` Eli Zaretskii
2014-03-19  9:01       ` arthur miller [this message]
2014-03-19 10:18         ` Phillip Lord
2014-03-19 18:17         ` Richard Stallman
2014-03-19 20:41           ` arthur miller
2014-03-19 22:26             ` Richard Stallman
2014-03-19 12:49       ` Ted Zlatanov
2014-03-19 12:53         ` arthur miller
2014-03-19 14:38         ` Stephen J. Turnbull
2014-03-19 16:36         ` Eli Zaretskii
2014-03-19 18:18         ` Richard Stallman
2014-03-20  6:23           ` Ted Zlatanov
2014-03-20 16:28             ` Eli Zaretskii
2014-03-20 16:42               ` David Kastrup
2014-03-20 16:43               ` arthur miller
2014-03-20 16:59               ` David Engster
2014-03-20 17:25                 ` arthur miller
2014-03-20 17:41                   ` David Engster
2014-03-20 17:52                     ` arthur miller
2014-03-20 20:05                 ` Johan Bockgård
2014-03-20 20:08                   ` David Engster
2014-03-20 20:07               ` Ted Zlatanov
2014-03-20 17:04             ` Matthew Leach
2014-03-19 16:20       ` Josh
2014-03-26 21:21 ` Mathias Dahl
2014-03-26 21:35   ` Lennart Borgman
2014-03-28  4:37     ` Lennart Borgman
2014-03-28 15:26       ` Richard Stallman
2014-03-28 16:10         ` Lennart Borgman
2014-03-30  0:24           ` Richard Stallman
2014-03-30  1:01             ` Lennart Borgman

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=DUB111-W2666850D0577A6531691EB967F0@phx.gbl \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).