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

Broken File Bits Generated in Working Directory #44

Open
monovich opened this issue Aug 4, 2020 · 0 comments
Open

Broken File Bits Generated in Working Directory #44

monovich opened this issue Aug 4, 2020 · 0 comments

Comments

@monovich
Copy link

monovich commented Aug 4, 2020

I am using Sublime with SendCode, Terminus, radian (though I sometimes use regular R console), and R-IDE with great success. Other than the terminus/radian slow-down bug this report is the only issue I've had with this configuration.

In short, somewhat inconsistently and infrequently, I will notice that after running some code in an R session with the aforementioned configuration, I will end up with random improperly formatted files in my working directory. The names of these files almost always includes lines of code run in my scripts. Examples names include:

cale(t(transformed_counts), center=TRUE, scale=TRUE)) ->-

eaRes = fgsea(pathways = msigdbr(species = "Mus musculus", category = "H"),

(x=NES,

sic() +

(fill = -log10(padj),

v(path) ->-

For several of these, the functions being executed are pretty easily distinguished. When these files are opened you are presented with various text. I've included a snippet below of one such file:

               S�SU�UM�MM�MA�AR�RY�Y O�OF�F L�LE�ES�SS�S C�CO�OM�MM�MA�AN�ND�DS�S

  Commands marked with * may be preceded by a number, _�N.
  Notes in parentheses indicate the behavior if _�N is given.
  A key preceded by a caret indicates the Ctrl key; thus ^K is ctrl-K.

  h  H                 Display this help.
  q  :q  Q  :Q  ZZ     Exit.
  ---------------------------------------------------------------------------

                       M�MO�OV�VI�IN�NG�G

  e  ^E  j  ^N  CR  *  Forward  one line   (or _�N lines).
  y  ^Y  k  ^K  ^P  *  Backward one line   (or _�N lines).
  f  ^F  ^V  SPACE  *  Forward  one window (or _�N lines).
  b  ^B  ESC-v      *  Backward one window (or _�N lines).
  z                 *  Forward  one window (and set window to _�N).
 w                 *  Backward one window (and set window to _�N).
 ESC-SPACE         *  Forward  one window, but don't stop at end-of-file.
 d  ^D             *  Forward  one half-window (and set half-window to _�N).
 u  ^U             *  Backward one half-window (and set half-window to _�N).
 ESC-)  RightArrow *  Right one half screen width (or _�N positions).
 ESC-(  LeftArrow  *  Left  one half screen width (or _�N positions).
 ESC-}  ^RightArrow   Right to last column displayed.
 ESC-{  ^LeftArrow    Left  to first column.
 F                    Forward forever; like "tail -f".
 ESC-F                Like F but stop when search pattern is found.
 r  ^R  ^L            Repaint screen.
 R                    Repaint screen, discarding buffered input.
    ---------------------------------------------------
    Default "window" is the screen height.
    Default "half-window" is half of the screen height.
---------------------------------------------------------------------------

I suspect there is an infrequent trigger for this behavior but I'm not exactly sure what it is. Any help would be much appreciated.

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

No branches or pull requests

1 participant