all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ship Mints <shipmints@gmail.com>
To: "Sebastián Monía" <sebastian@sebasmonia.com>
Cc: Mariano Montone <marianomontone@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-info command?
Date: Thu, 31 Oct 2024 09:13:44 -0400	[thread overview]
Message-ID: <CAN+1HbpCs1PFuGAQV4J1ee_Nri9+CLRzKZRJiibZjGQjZw35vQ@mail.gmail.com> (raw)
In-Reply-To: <thqn7c9ozagr.fsf@sebasmonia.com>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

In case my approach is of use, for "non production" Emacs versions or
instances, I change the background color of the mode-line and set the color
of 'internal-border. I set a "test flag" either on version or by
command-line argument "--test". The mode-line color shows fine in tty and
GUI. I can't easily get confused that way.

On Thu, Oct 31, 2024 at 9:09 AM Sebastián Monía <sebastian@sebasmonia.com>
wrote:

> Mariano Montone <marianomontone@gmail.com> writes:
>
> > 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.
>
> I don't think I had a need for one, I do use 'M-x version' somewhat
> regularly: I tend to run pretest or an organic, locally sourced, fair
> trade version(1) and sometimes I forget which one I am using.
>
> The 'emacs-version' command inserts the version string at point with
> prefix argument. Maybe it can show this buffer with double prefix arg?
> Or negative argument.
>
>
>
> (1) which means, version I compile myself.
>
> --
> Sebastián Monía
> https://site.sebasmonia.com/
>
>

[-- Attachment #2: Type: text/html, Size: 1796 bytes --]

  reply	other threads:[~2024-10-31 13:13 UTC|newest]

Thread overview: 5+ 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 [this message]
2024-10-31 14:43 ` Eli Zaretskii
2024-10-31 14:48   ` Mariano Montone

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=CAN+1HbpCs1PFuGAQV4J1ee_Nri9+CLRzKZRJiibZjGQjZw35vQ@mail.gmail.com \
    --to=shipmints@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=marianomontone@gmail.com \
    --cc=sebastian@sebasmonia.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.