From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3214 invoked from network); 26 Jan 2022 21:30:30 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 26 Jan 2022 21:30:30 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nCps4-002oVX-Eh for ml@inbox.vuxu.org; Wed, 26 Jan 2022 15:30:28 -0600 Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.94.2) (envelope-from ) id 1nCps3-003YbQ-Le for ml@inbox.vuxu.org; Wed, 26 Jan 2022 15:30:27 -0600 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.94.2) (envelope-from ) id 1nCps2-003YbK-R6 for ding@lists.math.uh.edu; Wed, 26 Jan 2022 15:30:26 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nCps0-002oVD-Mz for ding@lists.math.uh.edu; Wed, 26 Jan 2022 15:30:26 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=hNOxGhjZ223vu5mZtE1eM6fuYYVsLjcIH5QRQ+8zUBU=; b=gFFmZBte6dnzdRIRZMfsuSyPiQ a0Q8H2FhcXV6CYSFMS2Cz7uKUovUYh42Fnyn4TuRlkkerucVeYdqN3jmTy4X0C4O3FL29eyhhJjP0 BjoKLtZ+Ej0Cg2akPpza5dXp5+6GlPV/y7zPcuf7mpnOg5kRMHj9OQqziT19wpt3eArA=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nCprt-0006SL-Mx for ding@gnus.org; Wed, 26 Jan 2022 22:30:19 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nCprr-000807-Ei for ding@gnus.org; Wed, 26 Jan 2022 22:30:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: message-beginning-of-line behaves a bit strange Date: Wed, 26 Jan 2022 13:30:07 -0800 Message-ID: <874k5qxk0w.fsf@ericabrahamsen.net> References: <87mtjimc2k.fsf@mat.ucm.es> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cancel-Lock: sha1:f0y/BYNbBiW3fd27+nnlAoJF8dQ= List-ID: Precedence: bulk Uwe Brauer writes: > Hi > > I want to write a simple function that inserts always a specific word at the beginning of the subject line, either > > 1. If I want to compose a message and the subject is empty > > 2. Or I reply to message and the subject is not empty. > > So if I try > > (message-goto-subject) the cursor jumps > > 1. either (for an empty subject) > Subject: > ^ > so I could insert the word > > 2. If the subject is not empty then the cursor jumps to > Subject: stuff > ^ > So I have to call message-beginning-of-line and obtain > Subject: stuff Try `message-beginning-of-header' instead. Alternately, fooling with the value of (variable) `message-beginning-of-line' while calling (function) `message-beginning-of-line'.