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 28317 invoked from network); 27 Jan 2022 16:31:44 -0000
Received: from mx1.math.uh.edu (129.7.128.32)
  by inbox.vuxu.org with ESMTPUTF8; 27 Jan 2022 16:31:44 -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 <ding-owner+M38756=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1nD7gT-003RSc-5K
	for ml@inbox.vuxu.org; Thu, 27 Jan 2022 10:31:41 -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 <ding-owner+M38756=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1nD7gS-003azh-I0
	for ml@inbox.vuxu.org; Thu, 27 Jan 2022 10:31:40 -0600
Received: from mx2.math.uh.edu ([129.7.128.33])
	by lists1.math.uh.edu with esmtp (Exim 4.94.2)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1nD7gR-003azb-OM
	for ding@lists.math.uh.edu; Thu, 27 Jan 2022 10:31:39 -0600
Received: from quimby.gnus.org ([95.216.78.240])
	by mx2.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1nD7gP-00BQf5-Nz
	for ding@lists.math.uh.edu; Thu, 27 Jan 2022 10:31:39 -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=Frry4ix3KqjWXHwsIBAVbRiRlGDxjXpuB98+l6Efw9g=; b=DTeGtTj5WUnaDJfvYNidAT73lN
	OpG1OQo/Qn2bruAI3vgBue0hi5QFEPCE0CIfuY1LQ6VyhDlpSz/0sOVRsBW+egZERzptLTHcR9FV0
	gZ7k03CTuAXANu2fiVtITuYdvezZefnkDXwBiFU1KY/nYwNUPVB84bYJRd3gi8MGzUQA=;
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 <ding-account@m.gmane-mx.org>)
	id 1nD7gI-00005K-AI
	for ding@gnus.org; Thu, 27 Jan 2022 17:31:32 +0100
Received: from list by ciao.gmane.io with local (Exim 4.92)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1nD7gG-0000AR-U5
	for ding@gnus.org; Thu, 27 Jan 2022 17:31:28 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: ding@gnus.org
From: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: message-beginning-of-line behaves a bit strange
Date: Thu, 27 Jan 2022 08:31:22 -0800
Message-ID: <87y231uomd.fsf@ericabrahamsen.net>
References: <87mtjimc2k.fsf@mat.ucm.es> <874k5qxk0w.fsf@ericabrahamsen.net>
	<87czkdliut.fsf@mat.ucm.es> <87v8y5h0iv.fsf@zoho.eu>
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:1E4KR07uxs6IMMmEaNjVt4LU/os=
List-ID: <ding.gnus.org>
Precedence: bulk

Emanuel Berg <moasenwood@zoho.eu> writes:

> Uwe Brauer wrote:
>
>>> Uwe Brauer <oub@mat.ucm.es> writes:
>>
>>> Try `message-beginning-of-header' instead. Alternately,
>>> fooling with the value of (variable)
>>> `message-beginning-of-line' while calling (function)
>>> `message-beginning-of-line'.
>>
>> Great, I did
>>
>> (defun my-add-subject-test ()
>>   (interactive)
>>   (message-goto-subject)
>> ;  (message-beginning-of-line)
>>   (message-beginning-of-header 'subject)
>>   (insert "[Test] "))
>>
>> And this work nicely for both, empty and non empty
>> subject lines!
>
> ?! Subject twice?
>
> What kind of code is that? I mean
>
>   (message-goto-subject)
>   (message-beginning-of-header 'subject)
>
> Much better:
>
> `message-goto-subject' could have an optional formal parameter
> BEG so when the argument is non-nil it does
> (message-beginning-of-header 'subject) last.
>
> But at the very least (message-beginning-of-header 'subject)
> should imply (message-goto-subject) first.
>
> Or one could make HANDLE-FOLDED optional and when nil, go to
> the current line's header beginning.
>
> Subject should appear one time!

As Robert points out, the 'subject argument is actually meaningless,
the argument's actual name is HANDLE-FOLDED.
`message-beginning-of-header' acts on whatever header point is on, it
doesn't differentiate between headers.