Re: LyX Bug Tracker Password Reset Behavior
On Mon, Mar 07, 2022 at 06:00:45PM -0700, Joel Kulesza wrote: > On Mon, Mar 7, 2022 at 12:53 PM Scott Kostyshak wrote: > > > On Sun, Mar 06, 2022 at 10:32:06AM -0700, Joel Kulesza wrote: > > > Colleagues, > > > > > > I've tried to rest my "forgotten password" in the LyX bug tracker. > > > However, the emails it sends are failing to reach me (not my inbox or my > > > "junk" folder). > > > > > > Do we know whether everything is working as expected? > > > > > > Sorry for any inconvenience in this regard—I'm quite certain of my > > password > > > so I'm not sure what the issue is... > > > > Hi Joel, > > > > Arg sorry for that frustration. The bug tracker is pretty old, and > > certainly some strange things have happened because of it. I haven't > > heard of any recent strangeness along the lines that you've experienced > > but I'm also not surprised. I wish I could offer to transfer things to > > e.g., GitLab but I just don't have time. > > > > I don't know if there is a way for us to recover your account. Wait > > until someone more knowledgeable than I comes along before you try > > something. One hackish possibility is that I think it is easy to > > *delete* your account. I wonder if we delete your account and you make a > > new account with the same user name if trac will treat it continuously > > (e.g., if we search for bugs created by it shows both > > old ones and ones with your "new" account). > > > > Scott > > > > Scott, > > Thanks for these thoughts! Indeed, JMarc replied a bit after you and I > privately replied to propose a course of action that'll hopefully get me > back to submitting issues. Thanks to you both for your replies! Great, I'm glad there is hope. > Along those lines, you mentioned transitioning to Gitlab. That's something > I investigated ~1 year ago. I'm happy to share nascent (and partial) work, > but I'm unsure whether there are any privacy concerns of the metadata that > I propagated, which is why I'm not immediately sharing the link in this > note. > > From that work, I observe that the migration will be somewhat labor > intensive, and many of the formatting "niceties" of legacy issues will be > lost or at least severely diluted. I'm not entirely happy with the result, > which is why I didn't share progress before now, but perhaps the 90% > solution is acceptable for older issues acknowledging that the 100% > solution for issues and the other tightly integrated interface elements for > future issues (and work) is worth it. I provide this link in case we want > to revisit discussion on this point and to pursue this as an option. > > I'm happy to address comments, questions, or concerns in this regard. Thanks, Joel! I've been complaining several years that we should switch, but I don't do anything about it :). And I still have no plans to volunteer. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX Bug Tracker Password Reset Behavior
On Mon, Mar 7, 2022 at 12:53 PM Scott Kostyshak wrote: > On Sun, Mar 06, 2022 at 10:32:06AM -0700, Joel Kulesza wrote: > > Colleagues, > > > > I've tried to rest my "forgotten password" in the LyX bug tracker. > > However, the emails it sends are failing to reach me (not my inbox or my > > "junk" folder). > > > > Do we know whether everything is working as expected? > > > > Sorry for any inconvenience in this regard—I'm quite certain of my > password > > so I'm not sure what the issue is... > > Hi Joel, > > Arg sorry for that frustration. The bug tracker is pretty old, and > certainly some strange things have happened because of it. I haven't > heard of any recent strangeness along the lines that you've experienced > but I'm also not surprised. I wish I could offer to transfer things to > e.g., GitLab but I just don't have time. > > I don't know if there is a way for us to recover your account. Wait > until someone more knowledgeable than I comes along before you try > something. One hackish possibility is that I think it is easy to > *delete* your account. I wonder if we delete your account and you make a > new account with the same user name if trac will treat it continuously > (e.g., if we search for bugs created by it shows both > old ones and ones with your "new" account). > > Scott > Scott, Thanks for these thoughts! Indeed, JMarc replied a bit after you and I privately replied to propose a course of action that'll hopefully get me back to submitting issues. Thanks to you both for your replies! Along those lines, you mentioned transitioning to Gitlab. That's something I investigated ~1 year ago. I'm happy to share nascent (and partial) work, but I'm unsure whether there are any privacy concerns of the metadata that I propagated, which is why I'm not immediately sharing the link in this note. >From that work, I observe that the migration will be somewhat labor intensive, and many of the formatting "niceties" of legacy issues will be lost or at least severely diluted. I'm not entirely happy with the result, which is why I didn't share progress before now, but perhaps the 90% solution is acceptable for older issues acknowledging that the 100% solution for issues and the other tightly integrated interface elements for future issues (and work) is worth it. I provide this link in case we want to revisit discussion on this point and to pursue this as an option. I'm happy to address comments, questions, or concerns in this regard. Thanks again, Joel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX Bug Tracker Password Reset Behavior
Le 06/03/2022 à 18:32, Joel Kulesza a écrit : Colleagues, I've tried to rest my "forgotten password" in the LyX bug tracker. However, the emails it sends are failing to reach me (not my inbox or my "junk" folder). Do we know whether everything is working as expected? Sorry for any inconvenience in this regard—I'm quite certain of my password so I'm not sure what the issue is... Thank you, Joel I find this in our logs: 2022-03-06 16:41:34,272 Trac[api] INFO: Password reset user: jkulesza, jkule...@gmail.com 2022-03-06 16:41:35,766 Trac[notification] INFO: Sending notification through SMTP at localhost:25 to [u'jkule...@gmail.com'] 2022-03-06 16:41:35,869 Trac[api] INFO: Updated password for user: jkulesza I do not see anything wrong here, but of course I do not know what to look for. I can change you password through the trac interface, but I do not know whether this would be useful. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX Bug Tracker Password Reset Behavior
On Sun, Mar 06, 2022 at 10:32:06AM -0700, Joel Kulesza wrote: > Colleagues, > > I've tried to rest my "forgotten password" in the LyX bug tracker. > However, the emails it sends are failing to reach me (not my inbox or my > "junk" folder). > > Do we know whether everything is working as expected? > > Sorry for any inconvenience in this regard—I'm quite certain of my password > so I'm not sure what the issue is... Hi Joel, Arg sorry for that frustration. The bug tracker is pretty old, and certainly some strange things have happened because of it. I haven't heard of any recent strangeness along the lines that you've experienced but I'm also not surprised. I wish I could offer to transfer things to e.g., GitLab but I just don't have time. I don't know if there is a way for us to recover your account. Wait until someone more knowledgeable than I comes along before you try something. One hackish possibility is that I think it is easy to *delete* your account. I wonder if we delete your account and you make a new account with the same user name if trac will treat it continuously (e.g., if we search for bugs created by it shows both old ones and ones with your "new" account). Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: LyX 2.4.0 (IM policy.xml ban on eps/pdf conversions)
On Fri, Feb 04, 2022 at 10:36:57AM +, José Abílio Matos wrote: > On Wednesday, 2 February 2022 21.45.40 WET Pavel Sanda wrote: > > Jose, could I ask for pythonic help? > > We would need a routine in configure.py which check whether to remove > > eps->png > > conversion in case IM bans those conversions. That could be done this way by > > checking return status of the conversion. In bash that would be something > > like this: > > > > echo '%!PS' > /tmp/.lyx_configure_test.eps > > convert /tmp/.lyx_configure_test.eps /tmp/.lyx_configure_test.png > > if ! [ $? == 0 ] ; then > > # remove eps->png conversion from configure settings, i.e. set \converter > > "eps" "png" "" "" fi > > > > > > Completely different way would be mimicking what IM internally does with GS > > when converting eps->png. I already checked little bit and unfortunately it > > won't be oneliner if we want to get resolution right. But probably doable > > with additional script of our own. Pavel > > I will look into this in the weekend. > > > At some point I will want to overhaul the configure.py script. > The purpose is, among others, to simplify the code required to do this kind > of tests. > > The test above is relatively easy to do. > Something that I should, probably, take into account is the order of the > tests. > > In the sense that if we different \convert lines we probably retain the > last... > ping :) p -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Terminal messages on recent master
On Fri, Feb 25, 2022 at 09:40:33AM -0500, Scott Kostyshak wrote: > On Fri, Feb 25, 2022 at 02:53:04PM +0100, Jean-Marc Lasgouttes wrote: > > > > Le 22/02/2022 à 20:20, Scott Kostyshak a écrit : > > > On recent master (starting in the past week or so), I've seen the > > > following terminal messages on two different occasions: > > > > > >Unsupported return type 65 QPixmap in method "grab" > > >Unsupported return type 65 QPixmap in method "grab" > > >Unsupported return type 1087 QAction* in method "addAction" > > >Skipped method "setDefaultShortcuts" : Pointers are not supported: > > > QAction* > > > > > > I don't know what triggers them, as I usually see terminal messages > > > after I quit LyX. Is there any way to have LyX assert on them so I can > > > try to figure out how to reproduce? If not, any way to break on them > > > while running through gdb? > > > > I did some searching and it turns out that you can do > > (gdb) break write if 2==$rdi > > > > https://stackoverflow.com/questions/1538463/how-can-i-put-a-breakpoint-on-something-is-printed-to-the-terminal-in-gdb > > > > This breaks on the write() syscall on the condition that $rdi is equal to 2 > > (the descriptor associated to stderr). And no, I do not know what $rdi > > contains. > > > > Hope this helps. > > Cool, thanks. I will try this. The messages actually come from Okular, not LyX. They are triggered when I lock the screen and unlock. I'm not planning to look into them more. If I had more time, I would report this upstream but I think I will let this go. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Beamer example file: use relative offsets?
On Monday, 7 March 2022 12.57.59 WET Scott Kostyshak wrote: > Let's just leave things as is for now. Perhaps it would make sense for > me to eventually start a separate Beamer example file so that we can > keep the introduction simple. > > Scott That "smells" (I am thinking about cinnamon, do not ask :-D ) as the right solution. :-) -- José Abílio-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Beamer example file: use relative offsets?
On Mon, Mar 07, 2022 at 08:11:07AM +0100, Jürgen Spitzmüller wrote: > Am So., 6. März 2022 um 20:19 Uhr schrieb Scott Kostyshak >: > > > For example, see the attached screenshot, where I highlight the "6". The > > "6" means to trigger the action (in this case highlight in red) on the > > 6th slide. If we replace the 6 with "+-" or ".(1)", we get identical PDF > > output. The advantage of using relative off-sets in this case, is that > > if we add another item to the list, or we add another manual pause, the > > relative offset does not need to be changed, but the absolute reference > > would need to be changed (e.g., if we add an item before we would need > > to change the 6 to a 7). > > > > I think users should learn both, contextual and fixed offsets. As to the > mentioned example, I am undecided. Let's just leave things as is for now. Perhaps it would make sense for me to eventually start a separate Beamer example file so that we can keep the introduction simple. Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
