all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: marianomontone@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-info command?
Date: Fri, 01 Nov 2024 14:02:20 +0200	[thread overview]
Message-ID: <86cyjf17sj.fsf@gnu.org> (raw)
In-Reply-To: <867c9nbdj6.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 01 Nov 2024 09:48:13 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: emacs-devel@gnu.org
> Date: Fri, 01 Nov 2024 09:48:13 +0200
> 
> > Hello,
> >     what do you think of Emacs coming with an emacs-info command that shows
> > current Emacs build information. I miss a command that quickly shows info
> > about current Emacs.
> > My current implementation is very basic:
> > https://codeberg.org/mmontone/emacs-snippets/src/branch/master/emacs-info.el
> >
> > And shows a buffer with:
> > ----------------
> > Version: GNU Emacs 31.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version
> > 2.24.33, cairo version 1.18.0)
> >  of 2024-08-13
> > Features: CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ JPEG
> > LIBSELINUX LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG SECCOMP SOUND SQLITE3
> > THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER WEBP X11 XDBE XIM XINPUT2 XPM
> > GTK2 ZLIB
> > Native compilation: no
> > SVG: no
> > --------------
> 
> We could show more information at the end of 'C-h C-a'.

We could, but IMO we shouldn't: this is not what that command is for.



      reply	other threads:[~2024-11-01 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 12:49 emacs-info command? Mariano Montone
2024-10-31 13:08 ` Sebastián Monía
2024-10-31 13:13   ` Ship Mints
2024-10-31 14:43 ` Eli Zaretskii
2024-10-31 14:48   ` Mariano Montone
2024-11-01  7:48 ` Juri Linkov
2024-11-01 12:02   ` Eli Zaretskii [this message]

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=86cyjf17sj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=marianomontone@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 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.