From: Lars Ingebrigtsen <larsi@gnus.org>
To: Thuna <thuna.cing@gmail.com>
Cc: 53375@debbugs.gnu.org
Subject: bug#53375: [PATCH] Account for padding and content length in, tabulated-list-widen-current-column
Date: Fri, 21 Jan 2022 10:27:38 +0100 [thread overview]
Message-ID: <874k5xwi9h.fsf@gnus.org> (raw)
In-Reply-To: <CALUXaJhkU1y2rVXk9OrZXwSAvShbfBrAb-e-rSTuBNLTe-D9Tg@mail.gmail.com> (Thuna's message of "Thu, 20 Jan 2022 21:42:20 +0300")
Thuna <thuna.cing@gmail.com> writes:
> > That function is supposed to give reliable results, so if there are
> > modes it doesn't work in, that sounds like a bug.
>
> In that case debbugs itself needs a fix. It is possible that other
> tabulated-list derived modes will fail in a similar way so maybe a
> checkup is needed?
Sounds like it.
> > This change was small enough to apply without assigning copyright to the
> > FSF, but for future patches you want to submit, it might make sense to
> > get the paperwork started now, so that subsequent patches can be applied
> > speedily. Would you be willing to sign such paperwork?
>
> I am willing to sign the paperwork although I know neither how nor what
> it entails so some help would be appreciated.
Here's the form to get started, and here's the rationale behind it:
https://www.gnu.org/licenses/why-assign.en.html
Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
[What is the name of the program or package you're contributing to?]
Emacs
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your postal address here.]
[Which files have you changed so far, and which new files have you written
so far?]
next prev parent reply other threads:[~2022-01-21 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 21:40 bug#53375: [PATCH] Account for padding and content length in, tabulated-list-widen-current-column Thuna
2022-01-20 14:23 ` Lars Ingebrigtsen
2022-01-20 18:42 ` Thuna
2022-01-21 9:27 ` Lars Ingebrigtsen [this message]
2022-01-23 14:42 ` bug#53375: [PATCH] Correct wrong comparison operation in previous patch Thuna
2022-01-23 14:47 ` Lars Ingebrigtsen
2022-01-23 14:52 ` Thuna
2022-01-23 14:56 ` Lars Ingebrigtsen
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=874k5xwi9h.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53375@debbugs.gnu.org \
--cc=thuna.cing@gmail.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).