[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lyx-users
Subject:    Re: subscripts and superscripts display problem
From:       Richard Kimberly Heck <rikiheck () lyx ! org>
Date:       2018-07-09 2:57:45
Message-ID: 96054e5e-4fb3-4c3f-4fa8-66b3dc8e34a8 () lyx ! org
[Download RAW message or body]

On 07/08/2018 09:20 PM, David Pesetsky wrote:
> Thanks — reported.

I've got a patch there now that should fix this. Probably not until
2.3.2, though we'll see.

Riki


> > On Jul 8, 2018, at 8:00 PM, Richard Kimberly Heck <rikiheck@lyx.org
> > <mailto:rikiheck@lyx.org>> wrote:
> > 
> > On 07/08/2018 03:42 PM, Joel Kulesza wrote:
> > > 
> > > On Jul 8, 2018, at 10:49, David Pesetsky <pesetsk@mit.edu
> > > <mailto:pesetsk@mit.edu>> wrote:
> > > 
> > > > And an update:  I've discovered the problem previously reported
> > > > here (missed this for some reason when searching earlier):
> > > > 
> > > > https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor
> > > >  
> > > > -- with a reference to this bug
> > > > report: https://www.lyx.org/trac/ticket/10177
> > > > 
> > > > Is there an approved way to add my own "please fix this" to that
> > > > bug report from two years ago?
> > > 
> > > I’m not sure of it’s acceptability, but if I find an unresolved bug
> > > that I’m also afflicted by, I comment with the specifics (LyX
> > > version, OS, etc.) to (a) provide additional information about
> > > extent of effect, (b) indicate interest, and (c) get CC’d on any
> > > replies so I can follow and/or help debug as the issue is addressed
> > > by the dev team.
> > 
> > More info about such bugs is always welcome. And if more people seem
> > to be affected, then that does tend to bring attention to the issue.
> > 
> > Riki
> > 
> 
> -


[Attachment #3 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 07/08/2018 09:20 PM, David Pesetsky
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:E816373B-C395-40BB-8E72-3E99D368EA65@mit.edu">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Thanks — reported.</blockquote>
    <br>
    I've got a patch there now that should fix this. Probably not until
    2.3.2, though we'll see.<br>
    <br>
    Riki<br>
    <br>
    <br class="">
    <blockquote type="cite"
      cite="mid:E816373B-C395-40BB-8E72-3E99D368EA65@mit.edu">
      <div class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On Jul 8, 2018, at 8:00 PM, Richard Kimberly
              Heck &lt;<a href="mailto:rikiheck@lyx.org" class=""
                moz-do-not-send="true">rikiheck@lyx.org</a>&gt; wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta http-equiv="Content-Type" content="text/html;
                charset=utf-8" class="">
              <div text="#000000" bgcolor="#FFFFFF" class="">
                <div class="moz-cite-prefix">On 07/08/2018 03:42 PM,
                  Joel Kulesza wrote:<br class="">
                </div>
                <blockquote type="cite"
                  cite="mid:C75B2202-7B37-4D52-948E-D7C7FA065B39@gmail.com"
                  class="">
                  <div class=""><br class="">
                  </div>
                  <div class="">On Jul 8, 2018, at 10:49, David Pesetsky
                    &lt;<a href="mailto:pesetsk@mit.edu"
                      moz-do-not-send="true" class="">pesetsk@mit.edu</a>&gt;
                    wrote:<br class="">
                    <br class="">
                  </div>
                  <blockquote type="cite" class="">
                    <div class=""> And an update:  I've discovered the
                      problem previously reported here (missed this for
                      some reason when searching earlier):
                      <div class=""><br class="">
                      </div>
                      <div class=""><a
href="https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor"
  class="" moz-do-not-send="true">https://tex.stackexchange.com/questions/311041/subscript-and-superscript-in-lyx-leave-large-gaps-in-onscreen-editor</a></div>
  <div class=""><br class="">
                      </div>
                      <div class="">-- with a reference to this bug
                        report: <a
                          href="https://www.lyx.org/trac/ticket/10177"
                          class="" \
moz-do-not-send="true">https://www.lyx.org/trac/ticket/10177</a></div>  <div \
class=""><br class="">  </div>
                      <div class="">Is there an approved way to add my
                        own "please fix this" to that bug report from
                        two years ago?</div>
                    </div>
                  </blockquote>
                  <br class="">
                  <div class="">I’m not sure of it’s acceptability, but
                    if I find an unresolved bug that I’m also afflicted
                    by, I comment with the specifics (LyX version, OS,
                    etc.) to (a) provide additional information about
                    extent of effect, (b) indicate interest, and (c) get
                    CC’d on any replies so I can follow and/or help
                    debug as the issue is addressed by the dev team. <br
                      class="">
                  </div>
                </blockquote>
                <br class="">
                More info about such bugs is always welcome. And if more
                people seem to be affected, then that does tend to bring
                attention to the issue.<br class="">
                <br class="">
                Riki<br class="">
                <br class="">
              </div>
            </div>
          </blockquote>
        </div>
        <br class="">
        <div class="">
          <div style="color: rgb(0, 0, 0); letter-spacing: normal;
            text-align: start; text-indent: 0px; text-transform: none;
            white-space: normal; word-spacing: 0px;
            -webkit-text-stroke-width: 0px; word-wrap: break-word;
            -webkit-nbsp-mode: space; line-break: after-white-space;"
            class="">-</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic