unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
	Uwe Brauer <oub@mat.ucm.es>, Andrea Corallo <acorallo@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: having emacs-matlab in ELPA, finally. FSF paper signed
Date: Sat, 23 Nov 2024 14:22:26 +0100	[thread overview]
Message-ID: <87y11a13vx.fsf@mat.ucm.es> (raw)
In-Reply-To: CADwFkm=JR8_sRnQnwKLh89Sen1nYHkPKNuwkk747zkZ8fRNHHw@mail.gmail.com

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

>>> "SK" == Stefan Kangas <stefankangas@gmail.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>> +(defconst matlab-mode-version (package-get-version)
>> +  "Current version of MATLAB(R) mode.")

> We have tried to discourage the addition of such variables and commands,
> given that one can always find that information by other means,
> e.g. interactively with `describe-package` or from Lisp:

>     (package-desc-version (cadr (assq 'foo package-alist)))

So you want me use just that string 
well (package-desc-version (cadr (assq 'matlab-mode package-alist)))
I presume 

in matlab.el (and matlab-mode.el)?

What's about our current setting 

(defconst matlab-mode-version "6.2"
  "Current version of MATLAB(R) mode.")

Which we need for MELPA? 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5684 bytes --]

  reply	other threads:[~2024-11-23 13:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 12:45 having emacs-matlab in ELPA, finally. FSF paper signed Uwe Brauer
2024-08-06 21:55 ` Andrea Corallo
2024-08-07 17:03   ` Uwe Brauer
2024-08-07 17:54     ` Andrea Corallo
2024-08-12 11:20     ` Philip Kaludercic
2024-08-12 11:33       ` Andreas Schwab
2024-08-12 11:38         ` Philip Kaludercic
2024-08-12 12:16       ` Uwe Brauer
2024-08-12 12:29         ` Philip Kaludercic
2024-08-12 14:58           ` Uwe Brauer
2024-08-12 15:06             ` Philip Kaludercic
2024-08-12 15:17               ` Uwe Brauer
2024-08-12 16:11                 ` Philip Kaludercic
2024-11-22 16:12           ` Uwe Brauer
2024-11-23 10:30             ` Philip Kaludercic
2024-11-23 12:07               ` Stefan Kangas
2024-11-23 13:22                 ` Uwe Brauer [this message]
2024-11-23 19:13                   ` Stefan Kangas
2024-11-23 13:19               ` Uwe Brauer via Matlab-emacs-discuss
2024-11-23 13:30               ` having emacs-matlab in ELPA, finally. FSF paper signed, " Uwe Brauer

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=87y11a13vx.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=stefankangas@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 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).