> -Original Message-
> From: Guy Harris [mailto:g...@alum.mit.edu]
> Sent: Wednesday, December 25, 2019 4:50 PM
> To: Maynard, Chris
> Cc: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Wireshark-commits] master 8d65ccf: Show
> answers a line at a time, after the
On Dec 25, 2019, at 1:35 PM, Maynard, Chris wrote:
> On Dec 25, 2019, at 3:19 PM, Guy Harris wrote:
>
>> And, given that, is there any need to show the full text in the top-level
>> item?
>
> Well, showing the full text allows for full "Copy -> Value" to continue to
> work, and including
> -Original Message-
> From: Guy Harris [mailto:g...@alum.mit.edu]
> Sent: Wednesday, December 25, 2019 3:19 PM
> To: Maynard, Chris
> Cc: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Wireshark-commits] master 8d65ccf: Show
> answers a line at a time, after the
On Dec 25, 2019, at 10:44 AM, Maynard, Chris
wrote:
> Or revert this change so whois.answer reflects the entire answer again, but
> add each line underneath the answer using a different filter, such as
> "whois.answer.line"?
We could, but I think going back to the way it was before would be
> -Original Message-
> From: Guy Harris [mailto:g...@alum.mit.edu]
> Sent: Wednesday, December 25, 2019 1:23 PM
> To: Developer support list for Wireshark
> Cc: Maynard, Chris
> Subject: Re: [Wireshark-dev] [Wireshark-commits] master 8d65ccf: Show
> answers a line at a time, after the
On Dec 25, 2019, at 9:21 AM, Maynard, Chris via Wireshark-dev
wrote:
> With this change, it's no longer possible to right-click on the answer,
> choose "Copy -> Value" and easily obtain the *entire* answer. Now, you would
> have to copy each line one at a time to retrieve it.
That's not
> -Original Message-
> From: Wireshark-commits [mailto:wireshark-commits-boun...@wireshark.org]
> On Behalf Of Wireshark code review
> Sent: Sunday, December 22, 2019 1:01 AM
> To: wireshark-comm...@wireshark.org
> Subject: [Wireshark-commits] master 8d65ccf: Show answers a line at a time,
