unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Mathias Dahl <mathias.dahl@gmail.com>
Cc: arthur miller <arthur.miller@live.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: "Adobe Brackets like" editing in emacs
Date: Fri, 28 Mar 2014 05:37:20 +0100	[thread overview]
Message-ID: <CANbX3660YkcmHsb64iYZa2in=T+244EU83DiC3-P+68p5a0Q7g@mail.gmail.com> (raw)
In-Reply-To: <CANbX366K1JRpxLg-2nAHrv+TjBkA8m6+K2SBwp9_v78HDcqjyw@mail.gmail.com>

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

I just took a closer look to see if someone did not make a better version
of Brackets since brackets lacks a lot of functionality. Google did. They
integrated something like it in the browser. Take a look at Workspaces here
and test it in Chrome. Amazing.

Chrome DevTools Revolutions 2013 - HTML5 Rocks
http://www.html5rocks.com/en/tutorials/developertools/revolutions2013/


On Wed, Mar 26, 2014 at 10:35 PM, Lennart Borgman <lennart.borgman@gmail.com
> wrote:

> I have tested Brackets a bit the latest days, using it beside Emacs. It
> was not as integrated to the browser as I thought, but it is still useful.
> I have used it to edit CSS files and mixed files. It looks up all the
> places that it think might apply to an element in HTML. Unfortunately it
> does not seem to have one of those features I really would like: Parsing
> CSS media queries. It does not tell me which media query is used where and
> what the limits are for them. It does not even show the media queries at
> all in the Quick Edit (which is the feature we are discussing).
>
> I think it is the same for CSS classes.
>
> I guess they just stopped the development before implementing such useful
> features. It is of course quite a bit more complex to implement that part,
> both on the parsing level and UI level.
>
> Still, it is useful. And implementing those simple features in Emacs would
> not be that hard, I think. A crucial part would be to setup the connection
> between different files. (A little bit of that is in nXhtml.)
>
> And yes, it could be used with other languages too. Perhaps it can be
> useful for class-based languages, but that requires good parsing.
>
>
>
> On Wed, Mar 26, 2014 at 10:21 PM, Mathias Dahl <mathias.dahl@gmail.com>wrote:
>
>> Hi Arthur,
>>
>> This is a very interesting feature! Not only would it be useful for the
>> scenario described by you and others in this thread, but I also think it
>> would be useful for temporarily showing definitions from another place in
>> the same file that you are editing. Sure, there are tooltips, overlays and
>> whatnot that can do the same thing ("intellisense") but sometimes actually
>> seeing the full definition right where you are might be useful. No need to
>> jump back and forth, with a key you could show the definition of a function
>> where you are, and with another key it would be hidden. You would be able
>> to copy pieces of text from it and whatever. That being said, I have never
>> ever seen a feature like this before, and that could be an indication that
>> it is not actually useful, or no-one has thought of a crazy idea before the
>> Adobe people did it...
>>
>> /Mathias
>>
>>
>> On Tue, Mar 18, 2014 at 2:29 PM, arthur miller <arthur.miller@live.com>wrote:
>>
>>> Hi,
>>>
>>> my name is Arthur, and I just subscribed to this list. Though I am new
>>> to this list, I am not so new to Emacs.I have just a question/thought about
>>> a feature I would like see in Emacs, hope you don't mind.
>>>
>>> Lately Adobes Brackets editor has got some popularity (It seems to be
>>> pretty much Emacs on javascript). I am not really into using it full time,
>>> since I am good with Emacs, but I do like the idea of mulitple file editing
>>> in one buffer. It is like context-aware multi-file editing or what it
>>> should be called. They use it to edit css or javascript while editing html
>>> file, så that one does not have to switch between buffers/files. It seems
>>> pretty handy, and I would kind-a like to see implementation for C/C++
>>> (macros, templates) and so on.
>>>
>>> I think it shouldn't be impossible to do now, since Emacs already can
>>> split window and show multiple buffers. How difficult would it be to add a
>>> mode/feature to "expand" a buffer (split window) under the current line and
>>> load exact part of a file with of course correct langauge mode and so on. I
>>> guess semantic package would be needed since it seems to be similar context
>>> awareness as it is needed for code completition.
>>>
>>> I am not knowledgable about Emacs internals, so I don't really know
>>> where to hack, but wonder if something similar is already implemented or
>>> "on the way".
>>>
>>>
>>>
>>
>

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

  reply	other threads:[~2014-03-28  4:37 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
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 [this message]
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='CANbX3660YkcmHsb64iYZa2in=T+244EU83DiC3-P+68p5a0Q7g@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=mathias.dahl@gmail.com \
    /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).