unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Elijah G <eg642616@gmail.com>
Cc: sbaugh@catern.com, sbaugh@janestreet.com, philipk@posteo.net,
	emacs-devel@gnu.org, luangruo@yahoo.com
Subject: Re: [PATCH] Flymake Support Indicator Errors in Margin
Date: Sun, 07 Apr 2024 08:47:58 +0300	[thread overview]
Message-ID: <86msq5206p.fsf@gnu.org> (raw)
In-Reply-To: <CACnP4NKfA6LLzS5wEk0thS0+w6YLgEMvgesScT7z9OsJSgtXeg@mail.gmail.com> (message from Elijah G on Sat, 6 Apr 2024 14:14:34 -0600)

> From: Elijah G <eg642616@gmail.com>
> Date: Sat, 6 Apr 2024 14:14:34 -0600
> Cc: sbaugh@catern.com, sbaugh@janestreet.com, philipk@posteo.net, 
> 	emacs-devel@gnu.org, luangruo@yahoo.com
> 
> > Last, but not least: please mention this change (and the new user
> > options) in NEWS and in the Flymake manual.
> 
> Thank you, I've now fixed the patch and documented the changes done.

See below for some additional comments.

> Also I have a question, Do I need to assign copyright each time
> that I want to contribute to Flymake?

No, you assign the copyright for past and future changes, and you do
it only once.

Did you start the paperwork already?  I don't see your assignment on
file, so if you haven't started the paperwork, now is the time to do
it.  Let me know if you need me to send you the form to fill and the
instructions, to start the paperwork.

> I have a lot of ideas that I would like to contribute.

Thanks, looking forward to your contributions.

> --- a/doc/misc/flymake.texi
> +++ b/doc/misc/flymake.texi
> @@ -309,6 +309,11 @@ Customizable variables
>  A custom face for highlighting regions for which a note has been
>  reported.
>  
> +@item flymake-indicator-type
> +Which indicator type should Flymake use.

Suggest to reword:

  The indicator type which Flymake should use to indicate lines with
  errors or warnings.

> +@item flymake-margin-indicators-string
> +A List used for specify string, face and error types to
> +use in the margin indicators.

Suggest to reword:

  Specifies the string and face to use for the margin indicators, for
  each error type.

> +@item flymake-autoresize-margins
> +If non-@code{nil}, will resize margins either @code{flymake-mode} is
> +non-@code{nil} or @code{nil}.

Something is wrong with this sentence.  You probably mean

   If non-@code{nil}, Flymake will resize the margins when
   @code{flymake-mode} is turned on or off.

> +@item
> +@cindex margin of diagnostic
> +@code{flymake-margin-string}, an string displayed in the margin
                                 ^^^^^^^^^
"a string"

> +The value actually follows the syntax of @code{flymake-margin-indicators-string}
> +(@pxref{Customizable variables}). It is overridden by any
                                   ^^
Two spaces between sentences, please.

> ++++
> +*** New user option 'flymake-indicator-type'.
> +This user option controls which error indicator type Flymake should use
> +in current buffer. Depending on your preference, this can either use
                    ^^
Likewise.

> +*** New user option 'flymake-margin-indicators-string'

All heading lines in NEWS should end in a period.

> +It controls the string, their face and type error to display in
> +margin indicators.

  It controls, for each error type, the string and its face to display
  as the margin indicator.

> +*** New user option 'flymake-autoresize-margins'

Missing period at the end.

> +When non-nil, Flymake will resize margins either `flymake-mode` is
> +non-nil or nil.

See above for correction in the manual, I think the same wording
should be used here.

Also, please quote 'like this', not `like this` (here and elsewhere in
the patch for NEWS).

> +*** New user option 'flymake-margin-indicator-position'

Period missing at the end.

> +It controls which position should Flymake show margin indicators.

  It controls which margin (left or right) is used for margin
  indicators.

> +(defvar-local flymake--original-margin-width nil
> +  "Store original margin width.
> +Used by `flymake--resize-margins' for restore original margin width
                                     ^^^^^^^^^^^
"for restoring"



  reply	other threads:[~2024-04-07  5:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 23:18 [PATCH] Flymake Support Indicator Errors in Margin Elijah G
2024-03-12  9:24 ` Philip Kaludercic
2024-03-12 17:22   ` Elijah G
2024-03-13 12:18     ` Eli Zaretskii
2024-03-14  1:50       ` Elijah G
2024-03-14 11:05         ` Eli Zaretskii
2024-03-14 11:28           ` João Távora
2024-03-14 15:35           ` Elijah G
2024-03-16 11:10             ` Eli Zaretskii
2024-03-17 16:44               ` bird
2024-03-17 17:01                 ` Eli Zaretskii
2024-03-17 17:34                 ` Elijah G
2024-03-17 18:43                   ` bird
2024-03-17 19:21                     ` Elijah G
2024-03-25  1:46                       ` Elijah G
2024-03-27  0:13                         ` sbaugh
2024-03-27  0:36                           ` Elijah G
2024-03-27 21:29                           ` Elijah G
2024-03-28  6:01                             ` Eli Zaretskii
2024-03-28 17:34                               ` Elijah G
2024-04-06 11:36                                 ` Eli Zaretskii
2024-03-28  7:30                             ` Juri Linkov
2024-03-28 17:44                               ` Elijah G
2024-04-06 11:35                             ` Eli Zaretskii
2024-04-06 20:14                               ` Elijah G
2024-04-07  5:47                                 ` Eli Zaretskii [this message]
2024-04-07 17:20                                   ` Elijah G
2024-04-18  9:10                                     ` Eli Zaretskii
2024-03-19  7:03                   ` Augusto Stoffel
2024-03-17 17:49                 ` Elijah G
2024-03-19  7:04                   ` Augusto Stoffel

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=86msq5206p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eg642616@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=philipk@posteo.net \
    --cc=sbaugh@catern.com \
    --cc=sbaugh@janestreet.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).