From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id A1A6A386183E for ; Tue, 26 Sep 2023 14:42:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A1A6A386183E Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1695739351; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nLQFDBTCQpd51HvbMtP8gRzwx0VW7TAT0LGOoiBMBxM=; b=AjgqBqaWpOUWMQEWCYq7klEsfea8Zphn3wd8o5UKZB4doyXdAbIr6GTXg/2rfNgq6XL7UN UChb/2f74f7GrXBLRZNxnWI1Np6QBwIQd3uorNPhOTAYaOmkfGicVxOQTPYnuLhZUNho1R DxsaBVHUDGM6rCdHQdtT+iQgPTyhMGA= Received: from mail-lj1-f199.google.com (mail-lj1-f199.google.com [209.85.208.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-468-uDcxT3-KPDqAK_mGj6G5YQ-1; Tue, 26 Sep 2023 10:42:30 -0400 X-MC-Unique: uDcxT3-KPDqAK_mGj6G5YQ-1 Received: by mail-lj1-f199.google.com with SMTP id 38308e7fff4ca-2bff6dcbccaso132040481fa.1 for ; Tue, 26 Sep 2023 07:42:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695739348; x=1696344148; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nLQFDBTCQpd51HvbMtP8gRzwx0VW7TAT0LGOoiBMBxM=; b=kHhWr+wDxxKapG4dAPhmNe1u/CKJKQkoUy9iVJiTMlneTegnMXkiDMfHbwDoWjOFNt 04AdNHQuuntzfRboXG9Ftzic7fwk1jdn+K7BDGu94bKXNToyy8M4XwgbVX0uM7F+1lFQ gAPPSU8uCJHfydE6p6q7cJXc69cJ+eevf9EtH5lFSwMj2hEAi2xU0aVoUC4AdTCnEaNp U947IdXmHe5gVaz52NTKc30AspvAFcmJBcFDwahUCwBGdNSArXgpir955T6oWDT4YD/j i4ro3UOxi6QoEZ2sP0SJXhSKfyvvKa44+RHxJlN3yKwv2RK7OqT/4TmgfdiTiS77zJmZ AhKg== X-Gm-Message-State: AOJu0Yyy0QpkBxGhznXwnFkmTQgzMh+mnhP/WOdlzM0gLYwOBIOdHI4t Hi/gRMG4/hOmgRXrPwTKrO/6R0AdJi09+zgUCY3zHftcnBTkAmk1jkSA7TW2QH2MH7kXQGirsrM 7MJjhOPy0IGLuhjbKAOnXwDDt/aR+5w== X-Received: by 2002:a2e:b173:0:b0:2bd:58b:3a0b with SMTP id a19-20020a2eb173000000b002bd058b3a0bmr7853498ljm.50.1695739347927; Tue, 26 Sep 2023 07:42:27 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFlhkDClXx0KMowW0oaPuMJFSGAJB6Bcf3t3wvJ4Xf456EhAeP68mRJRD/AgbsQmF1GIu40Og== X-Received: by 2002:a2e:b173:0:b0:2bd:58b:3a0b with SMTP id a19-20020a2eb173000000b002bd058b3a0bmr7853485ljm.50.1695739347556; Tue, 26 Sep 2023 07:42:27 -0700 (PDT) Received: from localhost ([31.111.84.209]) by smtp.gmail.com with ESMTPSA id j26-20020a170906831a00b00997d7aa59fasm8034721ejx.14.2023.09.26.07.42.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Sep 2023 07:42:27 -0700 (PDT) From: Andrew Burgess To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [PATCH 07/10] gdb: add qMachineId packet In-Reply-To: <83zg2fmaj5.fsf@gnu.org> References: <94e68e6c1400ede2e9e46fc8ef76bd82aa533e0e.1692200989.git.aburgess@redhat.com> <83y1ib6j5x.fsf@gnu.org> <87r0nr9nz7.fsf@redhat.com> <83zg2fmaj5.fsf@gnu.org> Date: Tue, 26 Sep 2023 15:42:26 +0100 Message-ID: <87zg19vvvx.fsf@redhat.com> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Eli Zaretskii writes: >> From: Andrew Burgess >> Cc: gdb-patches@sourceware.org >> Date: Fri, 25 Aug 2023 15:49:00 +0100 >> >> Eli Zaretskii writes: >> >> > Btw, when a sentence starts with "See @ref", you could simplify by >> > using @xref, as that is its main purpose. >> >> When generating the 'info' docs @xref doesn't add the 'See' prefix, but >> when generating the pdf 'See' is added. I guess this explains why 'See >> @ref' is common throughout the GDB manual. > > No, @xref always produces "See". Where did you see it without "See"? Sorry Eli, I missed your reply here. I am using GNU texinfo 6.7, and I don't see @xref adding "See" when generating 'info' output format. When producing 'pdf' output I do see the "See" prefix. This is visible to me in the current GDB info page(s). For example, this paragraph in gdb.texinfo: If the architecture supports memory tagging, the @code{print} command will display pointer/memory tag mismatches if what is being printed is a pointer or reference type. @xref{Memory Tagging}. Is rendered like this in 'info' format: If the architecture supports memory tagging, the 'print' command will display pointer/memory tag mismatches if what is being printed is a pointer or reference type. *Note Memory Tagging::. I guess it has the '*Note ' prefix instead, but in contrast, this partial paragraph from gdb.texinfo: This command allows to control the information printed when the debugger prints a frame. See @ref{Frames}, @ref{Backtrace}, for a general explanation about frames and frame information. Is rendered like this in 'info' format: This command allows to control the information printed when the debugger prints a frame. See *note Frames::, *note Backtrace::, for a general explanation about frames and frame information. Which I think is nicer, for me starting the sentence with 'Note' doesn't seem as friendly. Thanks, Andrew