From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Phillip Lord <phillip.lord@newcastle.ac.uk>
Cc: Kaushal <kaushal.modi@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: beacon
Date: Fri, 16 Oct 2015 14:54:35 +0100 [thread overview]
Message-ID: <CAAdUY-KoQQnpgpmr0ymzh9ueJhzFquvBw5gcGe5esHuPM7gK-w@mail.gmail.com> (raw)
In-Reply-To: <87oafzq7op.fsf@newcastle.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
On 16 Oct 2015 2:11 pm, "Phillip Lord" <phillip.lord@newcastle.ac.uk> wrote:
>
>
>
> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
> > 2015-10-15 18:24 GMT+01:00 Kaushal Modi <kaushal.modi@gmail.com>:
> >>
> >> I haven't read either of the source codes, but is it similar to
lisp/cedet/pulse.el?
> >
> > Hm, I don't know. I'll look into what that does. Maybe it could have
> > saved me some implementation effort. :)
>
>
> I used pulse.el when I wrote eval-pulse.el and it's quite nice for the
> purpose.
>
> But then I discovered eval-sexp-fu and realised that I've wasted my time
> writing eval-pulse.
>
> Having some commonality for these visual distratctions kind of mode
> would be good -- it should allow configuration once.
Yeah, I had a look at pulse and there's definitely some common ground.
Beacon is really a user package, while pulse is more of a dependency lib.
I want to merge some of beacon's internals into pulse, so that beacon could
just a small extension on top of pulse, but that's not trivial. Their
internal logic is quite different, both in structure and in final outcome
(pulse fades a single color overlay by changing a font's background, while
beacon shrinks a multi-colour highlight by moving/deleting many overlays).
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next prev parent reply other threads:[~2015-10-16 13:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 17:02 [ELPA] New package: beacon Artur Malabarba
2015-10-15 17:24 ` Kaushal Modi
2015-10-15 17:26 ` Kaushal Modi
2015-10-15 17:33 ` Kaushal Modi
2015-10-15 21:27 ` Artur Malabarba
2015-10-15 21:37 ` Kaushal Modi
2015-10-15 21:44 ` Kaushal Modi
2015-10-15 22:13 ` Artur Malabarba
2015-10-15 22:27 ` Kaushal Modi
2015-10-15 22:40 ` Kaushal Modi
2015-10-16 8:06 ` Tassilo Horn
2015-10-15 22:47 ` Artur Malabarba
2015-10-15 21:21 ` Artur Malabarba
2015-10-16 13:11 ` Phillip Lord
2015-10-16 13:54 ` Artur Malabarba [this message]
2015-10-15 21:42 ` Rasmus
2015-10-15 17:36 ` Marcin Borkowski
2015-10-15 17:55 ` Kaushal Modi
2015-10-15 18:17 ` Artur Malabarba
2015-10-15 18:31 ` Howard Melman
2015-10-15 21:36 ` Artur Malabarba
2015-10-21 17:10 ` [ELPA] New package: on-screen (was: [ELPA] New package: beacon) Michael Heerdegen
2015-10-21 18:20 ` [ELPA] New package: on-screen John Wiegley
2015-10-21 18:54 ` John Wiegley
2015-10-21 19:04 ` Michael Heerdegen
2015-10-21 19:28 ` John Wiegley
2015-10-22 7:26 ` David Kastrup
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=CAAdUY-KoQQnpgpmr0ymzh9ueJhzFquvBw5gcGe5esHuPM7gK-w@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=phillip.lord@newcastle.ac.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.
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).