search

scruel / tampermonkey-scripts

Naïve scripts by naïve ideas.
41 stars 3 forks source link

Residual XXXSCUEDLXXX and XXXSCAESKXXX in rendering results #16

Closed lethefrost closed 1 year ago

lethefrost commented 1 year ago

Hi scruel, I understand this might be the current solution for the latex-markdown rendering order issue we discussed a little while ago at #12 . Looks like you are substituting _ with XXXSCUEDLXXX, and * with XXXSCAESKXXX in the GPT generated contents. However, there might be a bug. I have been seeing XXXSCUEDLXXX and XXXSCAESKXXX everywhere in the rendered ChatGPT's answers, in plain text, italic/ bold text, code block/ inline code... Could this be possibly caused by failing to replace the _ and *s back afterward?

image image image
scruel commented 1 year ago

Fixed, caused by the update by OpenAI.

lethefrost commented 1 year ago

It might be related to a force push I made which contains a typo, try 0.6.4.

I just updated to 0.6.4 but this problem still exists.

By the way, I further find that even though refreshing the page might sometimes fix the rendered results, the code copied from code blocks still contains the placeholders in it.

scruel commented 1 year ago

It might be related to a force push I made which contains a typo, try 0.6.4.

I just updated to 0.6.4 but this problem still exists.

By the way, I further find that even though refreshing the page might sometimes fix the rendered results, the code copied from code blocks still contains the placeholders in it.

Yeah, I just released 0.6.5

lethefrost commented 1 year ago

It might be related to a force push I made which contains a typo, try 0.6.4.

I just updated to 0.6.4 but this problem still exists. By the way, I further find that even though refreshing the page might sometimes fix the rendered results, the code copied from code blocks still contains the placeholders in it.

Yeah, I just released 0.6.5

The problems are still here for me in 0.6.5 (for both rendered and copied contents)

scruel commented 1 year ago

Really? For copy, it's another issue, lets keep it in another issue, but for rendering, I think I already solved, screenshot please?

scruel commented 1 year ago

@lethefrost For copy, fixed, try 0.6.6.

lethefrost commented 1 year ago

Really? For copy, it's another issue, lets keep it in another issue, but for rendering, I think I already solved, screenshot please?

sure, with 0.6.5, this is the screeshot:

image
scruel commented 1 year ago

@lethefrost I can only reproduced it while switching the conversations, it will be fixed later, can you be sure that you are using the lastest version? Try refresh the page and check again?

lethefrost commented 1 year ago

@lethefrost I can only reproduced it while switching the conversations, it will be fixed later, can you be sure that you are using the lastest version? Try refresh the page and check again?

Hi, I updated to 0.6.7 and seems like it is fixed! Both the rendering and copying issues. Thank you so much! Very nice work.