You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I commonly use this great package is to generate a markdown report for data-analysis work. However sometimes I find it too easy to (mistakenly) create a cell. For example sometimes I just want to comment lines out for debugging using IDE shortcut (which toggles #), a cell was created above, and often the time the cell ends with returning a huge dataframe, and therefore in the generated markdown files the whole dataframe was printed out.
Personally I find using '#' as markdown lines not a great idea, as it's too easy to create cells when you just want to comment lines out for debugging. I understand you must have your reasons for this choice, so could we add some other options to make it less easier to separate a cell? Let's say for example a markdown cell has to be created by multiline comments. It doesn't need to be the default but an option would be really handy.
The text was updated successfully, but these errors were encountered:
Hi,
I commonly use this great package is to generate a markdown report for data-analysis work. However sometimes I find it too easy to (mistakenly) create a cell. For example sometimes I just want to comment lines out for debugging using IDE shortcut (which toggles #), a cell was created above, and often the time the cell ends with returning a huge dataframe, and therefore in the generated markdown files the whole dataframe was printed out.
Personally I find using '#' as markdown lines not a great idea, as it's too easy to create cells when you just want to comment lines out for debugging. I understand you must have your reasons for this choice, so could we add some other options to make it less easier to separate a cell? Let's say for example a markdown cell has to be created by multiline comments. It doesn't need to be the default but an option would be really handy.
The text was updated successfully, but these errors were encountered: