From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Request: add cl-font-lock to Emacs or Elpa Date: Sun, 22 Mar 2020 13:54:01 -0400 Message-ID: References: <56660D97-604F-4C15-8961-D35F07E6F29B@spensertruex.com> <87y2rtech3.fsf@spensertruex.com> <87eetll4as.fsf@spensertruex.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="66969"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel To: Spenser Truex Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Mar 22 18:54:37 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jG4o1-000HIj-6e for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Mar 2020 18:54:37 +0100 Original-Received: from localhost ([::1]:48628 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jG4o0-0002hW-8i for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Mar 2020 13:54:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54280) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jG4nX-0002J4-6C for emacs-devel@gnu.org; Sun, 22 Mar 2020 13:54:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jG4nV-00086K-Vc for emacs-devel@gnu.org; Sun, 22 Mar 2020 13:54:06 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:36173) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jG4nV-00085A-Rg for emacs-devel@gnu.org; Sun, 22 Mar 2020 13:54:05 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 095C8100865; Sun, 22 Mar 2020 13:54:05 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 6F1171006FC; Sun, 22 Mar 2020 13:54:03 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1584899643; bh=xnvhP7emoE+yfnRHdmAOyD4GalGZNJ6ge+vyvOqpVtE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=KIdUL+1hcIc8ZLu1cX38DOdSj2QGfYNMjrAgAfZRALpG44EdIqsNM4ewAssZrZJVM 7UulAGwLxJ6OuRH6cVTLrWg4TkefualNkNLgDDPkJ9y9ZzLRcgCs735osipu/TsV0Z 7ltyGCWjXbk8RU7JUHA4glNx9gyMLeTThCCnEflTU+Eo17BDFR5vkJa9Le4UUkquog eV/FZFe6ghk745A/ag0LXGAz8EfudxS2tstjk4AYI0N+d59ySbCKrUptyqnfG3+FZx G5udNaJEPjnx3DZab7Opz910cSelegcM1lmyn4xmkI36MCYdE1ka2a5a6neAx8Q35I gwusjECpGqGHQ== Original-Received: from alfajor (unknown [104.247.241.114]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id E92EC120538; Sun, 22 Mar 2020 13:54:02 -0400 (EDT) In-Reply-To: <87eetll4as.fsf@spensertruex.com> (Spenser Truex's message of "Sat, 21 Mar 2020 15:40:59 -0700") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245688 Archived-At: >> Let's hope patience will resolve this problem. > Indeed, with current events it is unlikely to be resolved. > Currently I have waited 9 months. The email is president@sfsu.edu. 9 months??!? And now that I think about it: there shouldn't be any need for the university's president to sign anything, AFAIK. If you need paperwork from your employer (SFSU), I'm pretty sure there's someone lower in the "chain of command" with the authority needed to sign that paperwork. Have you asked assign@gnu.org for help? Maybe they have some good idea about what to do? > I've done a git-blame for myself. Here is the code I added. Before I > contributed the macro the code repeated the pattern it generates. If that's all there is, then it's not a problem: it's small enough not to need paperwork. Stefan