From: Lynn Winebarger <owinebar@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "chen.mingzheng" <chen.mingzheng@outlook.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Where is sr-speedbar.el upstream repo?
Date: Tue, 5 Jul 2022 12:56:30 -0400 [thread overview]
Message-ID: <CAM=F=bCayLCbMp=OvHzby5akb0vdBG9ZSxJBu5CLjO3US7V_Lg@mail.gmail.com> (raw)
In-Reply-To: <jwv1quzk15q.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On Tue, Jul 5, 2022, 11:57 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > I'm curious why is that happens. What are the responsibilities for
> > a maintainer
>
> Nobody can sue the maintainer for not doing its job, so in terms of real
> responsibilities there aren't any, but in terms of what's expected, it's
> mostly to be responsive and to care about the package.
>
I'm curious about why the same-frame functionality hasn't been absorbed
into the speedbar package itself. The appearance of a "project explorer"
that doesn't "dock" in the project frame has always been a jarring
disconnect from the way other IDEs implement this idiom for me.
[-- Attachment #2: Type: text/html, Size: 1231 bytes --]
next prev parent reply other threads:[~2022-07-05 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 23:21 Where is sr-speedbar.el upstream repo? chen.mingzheng
2022-07-05 0:38 ` Stefan Kangas
2022-07-05 0:51 ` chen.mingzheng
2022-07-05 1:26 ` Stefan Kangas
2022-07-05 1:59 ` chen.mingzheng
2022-07-05 6:56 ` Sebastian Rose
2022-07-05 9:34 ` chen.mingzheng
2022-07-05 12:03 ` Stefan Monnier
[not found] ` <TYCPR01MB5743F6F10A0573375954655681819@TYCPR01MB5743.jpnprd01.prod.outlook.com>
[not found] ` <jwv7d4rk5by.fsf-monnier+emacs@gnu.org>
2022-07-05 15:49 ` chen.mingzheng
2022-07-05 15:55 ` Stefan Monnier
2022-07-05 16:56 ` Lynn Winebarger [this message]
2022-07-05 18:39 ` Akib Azmain Turja
2022-07-05 18:40 ` Stefan Monnier
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='CAM=F=bCayLCbMp=OvHzby5akb0vdBG9ZSxJBu5CLjO3US7V_Lg@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=chen.mingzheng@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.