From: Kenjiro NAKAYAMA <nakayamakenjiro@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16398@debbugs.gnu.org, Kenjiro NAKAYAMA <nakayamakenjiro@gmail.com>
Subject: bug#16398: 24.3.50; [PATCH] eww: Tiny fix to display bookmark list.
Date: Sun, 19 Jan 2014 15:50:50 +0900 [thread overview]
Message-ID: <87k3dwo46t.fsf@dhcp-193-97.nrt.redhat.com> (raw)
In-Reply-To: <87a9esecsl.fsf@building.gnus.org>
They both don't have big problem.
Left side title cannot be longer than 80 characters,
right side title cannot copy its URL due to the clipping.
But we should be consistent in eww-list-bookmarks and eww-list-histories.
Lars, it depends on your taste. I will follow your judge.
Kenjiro
larsi@gnus.org writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>> Altough current eww bookmark list shows "URL" and "Title", it is better
>>>> that "Title" is left side and "URL" is right, in my opinion.
>>>> And it makes possible to display full URL withought clip.
>>> If one URL is long, won't this just push the display of all titles off
>>> to the right?
>>> I think titles are as important as the URLs in the display.
>>
>> The way I read the above, you seem to be in violent agreement.
>> What am I missing?
>
> Uhm, yeah. I misread the patch. But it doesn't seem to limit
> anything. If there's one title that's longer than 80 characters, normal
> users won't see any URLs in the listing.
next prev parent reply other threads:[~2014-01-19 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:19 bug#16398: 24.3.50; [PATCH] eww: Tiny fix to display bookmark list Kenjiro NAKAYAMA
2014-01-08 15:53 ` Ted Zlatanov
2014-01-18 18:32 ` Lars Ingebrigtsen
2014-01-19 3:07 ` Stefan Monnier
2014-01-19 5:55 ` Lars Ingebrigtsen
2014-01-19 6:50 ` Kenjiro NAKAYAMA [this message]
2014-01-19 15:31 ` Lars Ingebrigtsen
2014-01-20 16:09 ` Ted Zlatanov
2014-01-20 20:24 ` Lars Ingebrigtsen
2014-02-10 2:04 ` Ted Zlatanov
2014-12-07 19:32 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3dwo46t.fsf@dhcp-193-97.nrt.redhat.com \
--to=nakayamakenjiro@gmail.com \
--cc=16398@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.