unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 32893@debbugs.gnu.org
Cc: 910021@bugs.debian.org
Subject: bug#32893: Let him know source code is available
Date: Tue, 02 Oct 2018 05:46:17 +0800	[thread overview]
Message-ID: <87zhvxgx1y.fsf_-_@jidanni.org> (raw)
In-Reply-To: <87h8i5rg3k.fsf@jidanni.org>

B> most likely caused by missing recommended package emacs-el.

Dear bug-gnu-emacs, I got an idea for 32893@debbugs.gnu.org:
Show the same thing no matter if the user has the .els installed or not.
And when he clicks on it have a message: "Source code not available
because you don't have the .els installed."

Or next to the link have "(source code not installed)" etc. next to the
link so he knows before he clicks it.

Currently he has no clue that source code is actually available,
thus defeating the whole Free Software Movement!





  parent reply	other threads:[~2018-10-01 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r2h9ahig.fsf@tethera.net>
     [not found] ` <87tvm5pye2.fsf@jidanni.org>
     [not found]   ` <handler.910021.D910021.153840454221352.notifdone@bugs.debian.org>
2018-10-01 12:44     ` bug#32893: describe-variable doesn't metion what lisp file created the variable 積丹尼 Dan Jacobson
2018-10-01 12:51       ` Noam Postavsky
2018-10-01 13:08         ` 積丹尼 Dan Jacobson
2018-10-01 13:41           ` Noam Postavsky
2018-10-01 14:13             ` 積丹尼 Dan Jacobson
2018-10-01 13:43           ` Eli Zaretskii
2018-10-01 21:46       ` 積丹尼 Dan Jacobson [this message]
2018-10-01 22:56         ` bug#32893: Let him know source code is available Glenn Morris
2018-10-01 23:04           ` Glenn Morris
2018-10-02  0:28       ` bug#32893: GNU wishes Debian not split out .els anymore 積丹尼 Dan Jacobson

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=87zhvxgx1y.fsf_-_@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=32893@debbugs.gnu.org \
    --cc=910021@bugs.debian.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).