Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display multi-line comments better, from scripts, in the output window. #9327

Closed
rdstern opened this issue Jan 4, 2025 · 2 comments · Fixed by #9337
Closed

Display multi-line comments better, from scripts, in the output window. #9327

rdstern opened this issue Jan 4, 2025 · 2 comments · Fixed by #9337

Comments

@rdstern
Copy link
Collaborator

rdstern commented Jan 4, 2025

@lloyddewit and @N-thony Happy New Year both. I have been trying to improve the help file in R-Instat and this has led me to run the recent script from the new script directory in the R-Instat library.

It has given rise to a small(?) possibly general problem in the presentation of scripts in the output window. I think it has always been there, but perhaps it is a recent regression. It is the aspect that a multiline comment displays as a effectively a single line in the output window. Here is the beginning of a script from the agridat package, that I get to from the Insert button and Library. It is gomez nitrogen:

### Name: gomez.nitrogen
### Title: Soil nitrogen at three times for eight fertilizer treatments
### Aliases: gomez.nitrogen
### Keywords: datasets

### ** Examples


library(agridat)

In the output window it looks like this:

### Name: gomez.nitrogen### Title: Soil nitrogen at three times for eight fertilizer treatments### Aliases: gomez.nitrogen### Keywords: datasets### ** Examples

While examining issues on comments in scripts I am also reminded of issue #8568. That's a challenge for @N-thony or perhaps to0 be allocated?

@rdstern rdstern changed the title Display multi-ine comments better, from scripts, in the output window. Display multi-line comments better, from scripts, in the output window. Jan 4, 2025
@N-thony
Copy link
Collaborator

N-thony commented Jan 7, 2025

@lloyddewit and @N-thony Happy New Year both. I have been trying to improve the help file in R-Instat and this has led me to run the recent script from the new script directory in the R-Instat library.

It has given rise to a small(?) possibly general problem in the presentation of scripts in the output window. I think it has always been there, but perhaps it is a recent regression. It is the aspect that a multiline comment displays as a effectively a single line in the output window. Here is the beginning of a script from the agridat package, that I get to from the Insert button and Library. It is gomez nitrogen:

### Name: gomez.nitrogen
### Title: Soil nitrogen at three times for eight fertilizer treatments
### Aliases: gomez.nitrogen
### Keywords: datasets

### ** Examples


library(agridat)

In the output window it looks like this:

### Name: gomez.nitrogen### Title: Soil nitrogen at three times for eight fertilizer treatments### Aliases: gomez.nitrogen### Keywords: datasets### ** Examples

@rdstern, I have tried to reproduce the about and it seems fine on my side in the output window
image

@rdstern
Copy link
Collaborator Author

rdstern commented Jan 7, 2025

@N-thony that's great, and half-solves the problem - see below:

image

So when I start, I am not displaying R-commands in the output window. Then I have the problem mentioned. I then switched to display the commands and the problem goes away - as you say.

Is it easy to display the comments nicely in the output window when not displaying commands? If not, then I can live with that, and we can close the issue.

I also note we have the same problem in the Insert dialog. When there is a library code it displays without sensible line feeds. If you are able to solve the problem in the output window, would the same solution work there too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants