From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, emacs-devel@gnu.org
Subject: RE: systemd @ in filenames not supported by thing-at-point
Date: Fri, 29 Jul 2016 23:47:57 -0700 (PDT) [thread overview]
Message-ID: <c3285270-8381-46db-bcb6-3b92332e61f0@default> (raw)
In-Reply-To: <86shury87u.fsf@student.uu.se>
> > Please don't cross-post to emacs-devel and
> > help-gnu-emacs. Pick one. (In this case, the
> > latter might be better.)
>
> Phew! Because when you said "pick one", for
> a moment I thought *I* was supposed to make
> the pick!
You are. You judge which list you think is more
appropriate - for you and for others. Which list would
help you more? Which would help other users or Emacs
developers more?
> And why isn't this a devel issue?
Maybe it is. If you think it is, then post to emacs-devel.
From my understanding of your question, I thought (think)
it is better suited for help-gnu-emacs. But it is up to you
which you choose. My only request was not to cross-post the
question.
Is it a how-do-I-do-this question or a question about Emacs
development?
next prev parent reply other threads:[~2016-07-30 6:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 1:35 systemd @ in filenames not supported by thing-at-point Emanuel Berg
2016-07-30 5:42 ` Drew Adams
2016-07-30 6:02 ` Emanuel Berg
2016-07-30 6:47 ` Drew Adams [this message]
2016-07-30 7:22 ` Emanuel Berg
2016-07-30 14:45 ` Drew Adams
2016-07-30 15:33 ` Emanuel Berg
2016-07-30 16:19 ` Clément Pit--Claudel
2016-07-31 0:23 ` Emanuel Berg
2016-07-31 1:00 ` Clément Pit--Claudel
-- strict thread matches above, loose matches on Subject: below --
2016-07-30 1:31 Emanuel Berg
2016-07-30 5:41 ` Drew Adams
2016-07-30 6:07 ` Emanuel Berg
2016-07-30 6:43 ` Drew Adams
2016-07-30 17:29 ` Stefan Monnier
2016-07-30 18:01 ` Emanuel Berg
2016-07-30 6:48 ` Yuri Khan
2016-07-30 7:58 ` Emanuel Berg
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=c3285270-8381-46db-bcb6-3b92332e61f0@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=embe8573@student.uu.se \
/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.