From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Aaron Jensen Newsgroups: gmane.emacs.bugs Subject: bug#30553: 26.0.91; underline appears beneath line-spacing rather than beneath text Date: Mon, 26 Feb 2018 13:05:22 -0800 Message-ID: References: <83r2pf78x5.fsf@gnu.org> <83fu5v6kdi.fsf@gnu.org> <83371u6xc2.fsf@gnu.org> <83y3jf21wh.fsf@gnu.org> <83inaj1rk6.fsf@gnu.org> <83efl71o1u.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1519679051 15367 195.159.176.226 (26 Feb 2018 21:04:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Feb 2018 21:04:11 +0000 (UTC) Cc: Alp Aker , 30553@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 26 22:04:07 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eqPwN-0003gE-16 for geb-bug-gnu-emacs@m.gmane.org; Mon, 26 Feb 2018 22:04:07 +0100 Original-Received: from localhost ([::1]:33253 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqPyN-0006jN-OR for geb-bug-gnu-emacs@m.gmane.org; Mon, 26 Feb 2018 16:06:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33847) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqPyI-0006j1-D5 for bug-gnu-emacs@gnu.org; Mon, 26 Feb 2018 16:06:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqPyE-0001Gp-D1 for bug-gnu-emacs@gnu.org; Mon, 26 Feb 2018 16:06:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:54337) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eqPyE-0001Gj-9U for bug-gnu-emacs@gnu.org; Mon, 26 Feb 2018 16:06:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eqPyD-0004pX-TX for bug-gnu-emacs@gnu.org; Mon, 26 Feb 2018 16:06:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Aaron Jensen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 26 Feb 2018 21:06:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 30553 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 30553-submit@debbugs.gnu.org id=B30553.151967913118531 (code B ref 30553); Mon, 26 Feb 2018 21:06:01 +0000 Original-Received: (at 30553) by debbugs.gnu.org; 26 Feb 2018 21:05:31 +0000 Original-Received: from localhost ([127.0.0.1]:34001 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eqPxj-0004op-7A for submit@debbugs.gnu.org; Mon, 26 Feb 2018 16:05:31 -0500 Original-Received: from mail-qt0-f169.google.com ([209.85.216.169]:36607) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eqPxh-0004oc-3t for 30553@debbugs.gnu.org; Mon, 26 Feb 2018 16:05:29 -0500 Original-Received: by mail-qt0-f169.google.com with SMTP id c7so20526074qtn.3 for <30553@debbugs.gnu.org>; Mon, 26 Feb 2018 13:05:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rZkhR2a2LQRocuHhDHXEwMjF9o/Muujre9mzwYcIWQ4=; b=Gr2SUSg4huo/8EcSXf9tBGoXL7lk8whZRm5i9sr7t5lROqOE5q1mjlQJNQzLV4g8oI 6ZSx4XlZomSg2HAa6K4fvFnHYZHnbH1Bu9o1NZLFw3RFQPP9chjFNcsDNQMlFRPfah+E n394PRuCR2Zn7rQY4F2C8BHhOHryCF/Bn5E8FDG7K7ITGV540pEvRKM0ScyCvXl5vVg3 9akTZeh8/mWWgeBemX7zmSx3eYYv5uSmDWxfUT3jb/2PIS8JfRmT1Y73YrkKTtjxv6R5 Xy39Hi9IVLTKz4UXnc8vxEt0+2hQ4NkpXpA2oqFwCB7HgiraP4dE6xCAvNj9vM2W+NFh KHvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rZkhR2a2LQRocuHhDHXEwMjF9o/Muujre9mzwYcIWQ4=; b=mqBWYRmb8DydBd8LI70IIRc9FnS9TLAj7lzAN5k/WIU8/UFw3LlOLvNzF7cxGVRZ/T XYgXYFzQSaUMaj6c3LpmC4wlLQ50+u9ZOLW4UJYVlhv1BZnJQe6CpEt7MDiLM2Z3sygf oQ+6DkYPjO3f3gYM2Y1rFA6lKqEaeNg1PUcTegzd6bRTisXJMQyehR10zeGFRPWrBmWh GgkfywSPMtkRjxAJ17wn0E9pPZ+Ls2OzL17Rinve9HzilPhG9yTivyXt/SSYKPrZf7JT VnS+NdCJEanEhO5OCbYN2DK+wGlAiYOx3Bgi+TV0tTVyRH/992BXgl/tl8XLP4Urbe3I t0GA== X-Gm-Message-State: APf1xPB1+4D+pa+eMQBzr+QzDQGp+CaE3O/Ntj5kwV4GFFMaTam778iR gGzAHium2jG5NjNYzl7lCYf9u7F3tUpcrS5sqoA= X-Google-Smtp-Source: AG47ELuuX+kk9R6+a65j39mLiJ9ozYuepxq85Z9lgpNaHdUg7gbepbCpKKTKQeweqsRkUDoYgTCldFTS2rOElEiMAqo= X-Received: by 10.200.15.148 with SMTP id b20mr19030192qtk.301.1519679123505; Mon, 26 Feb 2018 13:05:23 -0800 (PST) Original-Received: by 10.237.54.65 with HTTP; Mon, 26 Feb 2018 13:05:22 -0800 (PST) In-Reply-To: <83efl71o1u.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:143680 Archived-At: On Mon, Feb 26, 2018 at 12:41 PM, Eli Zaretskii wrote: > Bug#30609 does not describe a bug, IMO. I hear you--I hesitated to report it as a bug. If you'd prefer I submit things like that to emacs-devel in the future I can do that instead. >> 2. It would be great if we could figure out a way to address >> bug#30609. > > I don't see how, and I told that much in that bug report. But I'm far > from being a GUI display expert, so maybe someone else will come up > with a solution. Understood, thanks. I'll think on it and look around. I have one idea that I'll repsond with. > IMO, it's better to make x-underline-at-descent-line a tristate > variable than add another boolean. I'd be happy to do that. I think that's a better solution. I assume that any non-nil other than some string or symbol (what is more common?) would behave as it does today and that that new value, maybe `font'? would behave as the new variable I introduced in my patch does. Does that sound right? Any advice on porting an existing boolean to a non-nil from a documentation or previous example standpoint would be helpful. Thank you.