unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Y. E." <yugenekr@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to have a variable always set for emacs --debug-init [solved]
Date: Tue, 29 Jun 2021 16:07:43 +0300	[thread overview]
Message-ID: <CAFCpf7BLHXNPFNnNpFHB11sLA_F-s4z0PVLREshMPWP9jwxt=A@mail.gmail.com> (raw)
In-Reply-To: <YNrwA2VrlzyzYecD@protected.localdomain>

Got it, thanks!

On Tue, Jun 29, 2021 at 1:08 PM Jean Louis <bugs@gnu.support> wrote:
>
> * Yuzhana Ego <yugenekr@gmail.com> [2021-06-29 10:36]:
> > > One can mark it free hand like [solved] in the
> > > subject, at least we
> > > know it is solved for the poster.
> >
> >
> > Thanks for the suggestion.  It seemed to me mailing lists matched
> > threads by the subject, so I expected it might break threading.
>
> Threads are constructed by using Message-IDs in the headers, and
> depend largely on users' software. It is not centrally maintained like
> a forum, so they can break unintentionally as well.
>
> > (Maybe there’s some  place describing basic mailing-lists guidelines
> > for newcomers but I didn’t find a one.)
>
> There is no general rule that I know.
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/



  reply	other threads:[~2021-06-29 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 13:57 How to have a variable always set for emacs --debug-init Y. E.
2021-06-28 15:00 ` Jean Louis
2021-06-28 15:10 ` Óscar Fuentes
2021-06-28 15:31   ` Y. E.
2021-06-28 16:59     ` Óscar Fuentes
2021-06-28 18:57       ` Jean Louis
2021-06-29  7:35         ` How to have a variable always set for emacs --debug-init [solved] Yuzhana Ego
2021-06-29 10:03           ` Jean Louis
2021-06-29 13:07             ` Y. E. [this message]
2021-06-28 15:24 ` How to have a variable always set for emacs --debug-init Arthur Miller

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='CAFCpf7BLHXNPFNnNpFHB11sLA_F-s4z0PVLREshMPWP9jwxt=A@mail.gmail.com' \
    --to=yugenekr@gmail.com \
    --cc=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /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. 
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).