When I copy code from Stackoverflow and paste it into my emacs window, it pastes the whole thing as one super-long line, losing all the line-breaks. What's the easiest way to un-wrap this so I get back the line-breaks? Or paste it differently into emacs so it preserves line-breaks?
[EDIT: I read this question too quickly --- the approach I outlined will help clean up a lot of things, but not OP's actual problem. FWIW, I can't reproduce on the only windows box I have here]
Related
When I try to replace code by Pasting code I copied it just leaves the old code there and instead copies the code I was trying to replace. It also does it if I first delete the old code and paste the new one, it just adds the old code again and adds it to my clipboard.
This problem started happening 2 days ago after starting to code in JavaScript. Not sure if that helps but if anyone knows how to fix this please tell me.
Thank you
I have tried changing the binding for pasting and that still hasn't worked. I have copied code then pasted it in notepad and that works it is just vscode.
I found the problem. Everytime I select something VS Code automatically copies it to my clipboard for some bizarre reason
Every time when i past some code snippets in Github reply box, it past with weird indentation... which i fix manually every time.. i could possibly indent/format it first in my code editor.. copy and paste directly.. which could work.. however when i am more in a rush.. and copy a block directly from my running code.. it kind of a hassle to format... or even worse when i type code directly there...
is there any browser extension? hide short-cut wizardry that im not aware of in Github to format and indent my reply quickly?
You might want to try: https://github.com/panzerdp/clipboardy, it does look like it keeps formatting not only in GitHub, but also SO and others.
Many other extensions that might be useful here: https://github.com/showcases/github-browser-extensions.
I'm trying to configure Vim so that it highlights extra closed brackets in Perl, for example ()). For unclosed brackets this works correctly the extra ( is highlighted red. But the extra closed brackets are not highlighted.
This issue is only present when syntax=perl. When I use syntax=c or syntax=vim the unmatched closed brackets are correctly highlighted.
Here is an example with syntax=perl. The first row is fine but in the second row the extra ) is not red. :(
Do you know any tricks or plugins that could solve this?
I've found some (very) old vim plugins like Highlight-UnMatched-Brackets but they didn't solve this issue for me.
It's possible that this is a bug in the syntax highlight for Perl. The project that keeps track of all the Perl-specific files that get fed back to the vim project is here: https://github.com/vim-perl/vim-perl (I'm one of the maintainers) If you think it's a bug in the syntax highlighting, then go ahead and submit an issue on GitHub.
You might also try using the syntax files in the vim-perl project in your local vim. I don't know what version of vim you're running, but it's possible newer support files will solve your problem.
I have been a programmer for a decade now, but I believe this is the first time I've ever asked a question on a forum. I just can't figure this out and can't find the answer already online.
I am trying to turn on CUA mode so that emacs is more bearable for a windows user (normal copy paste functions). I am running Windows 7 and installed emacs through the Lisp In A Box package. I understand that I need to add a line to my .emacs file or init.el file. I'm not sure which, but I can't find either in my Lip In A Box install directory. The emacs package install also did not come with any tutorials or help files, so its really hard to pick this up.
I am stuck, any help is greatly appreciated!
The .emacs can be found by looking at the answers to this similar question.
Regarding documentation and tutorials, it looks like the link you provided for "Lisp in a Box" says:
If you are new to Emacs, it is
recommended that you read the Emacs
Tutorial which you can access from
with Emacs by going to the Help menu,
or by typing Control-h, letting go,
and hitting t. A more extensive manual
is also available from the Help menu,
or on the web at
http://www.gnu.org/software/emacs/manual/.
Which makes it sound like the manual is there, and certainly the tutorial (I made bold the directions to get to the tutorial).
As far as other places to get information, there is a collection of screencasts on the wiki.
Your question doesn't specify whether or not you what to add to your .emacs to activate CUA mode. You can check out the CUA mode documentation on the wiki (which has links to the manual). The minimal installation is just adding this to your .emacs: (cua-mode t).
For GNU/Emacs, you can choose to use any one of the following three file names as the start-up configuration file:
${HOME}/.emacs
${HOME}/.emacs.el
${HOME}/.emacs.d/init.el
It would probably be a good idea to decide on one of the three options and then stick to it - the first one seems to be the most widely used one. In any case, ${HOME} stands for your home directory -- which is likely to be different from the Lisp In A Box install directory!
Coming from a Unix tradition, Emacs understands ~ (tilde) as an abbreviation for your home directory, so you can visit the .emacs file by typing:
C-x C-f ~/.emacs [ENTER]
(Note that the capital C is Emacs standard notation for a combination of the CTRL key and a second key, i.e. here you press CTRL-x CTRL-f which stands for "find-file" and will then ask you for a file name in the bottom part of the Frame (aka mini-buffer).)
If these are your first customizations, you will just see an empty buffer. Enter
;; start CUA mode every time Emacs starts
(cua-mode t)
and save the buffer with C-x C-s.
Next time you start Emacs, CUA mode should be turned on automatically.
What the others have told you is true: Simply adding (cua-mode t) to your dotfile would be sufficient. HOWEVER: Lisp in a box' Emacs doesn't load this file by default.
Therefore, be sure to edit the shortcut so that it does load the dotfile. This is important, because otherwise you would get weird behavior, where you would add the correct line to the dotfile, start emacs, and then not get cua mode. That would suck.
The reason it does this is to ensure that it starts a vanilla emacs everytime, instead of finding, say C:/_emacs and loading that instead, giving you another user's customizations and confusing you.
The flag for not loading an init file is -q or --no-init-file. Also make sure that --no-site-file is not there.
(I realize that this is an old post, but I found this while looking for something related, and I don't want people walking away frustrated over something that doesn't work.)
I was digging through the header files for SDL in Linux when I tried to open the file from the SDL library called "SDL_opengl.h" in Emacs. For some reason, it always causes it to crash. It opens just fine in Vim and in gedit.
Has anyone else had an issue with Emacs just plain refusing to open a particular file? What sort of things should I look for to find what is causing the problem? Mind you, I was able to open every other "SDL_*.h" file in that directory; just that one gives me trouble.
Much appreciated in advance!
I would be interested to see the exact error message, and stack trace if possible.
I suspect file encoding, special characters, file size, cc-mode parsing, or something like that to be the culprit. (emacs 22 and libsdl1.2 on ubuntu 9 with utf-8 screen works fine for me)
Converting my comment into an answer b/c the comments get cut off.
Try loading the file with
M-x find-file-literally
Since this (appears to) resolve the issue for giogadi, I think that points to perhaps the colorization of the buffer. cc-mode does its own colorization...
Oh goodness, I'm a dunce.
So I apparently underestimated both the size of the file AND the speed of Emacs in opening said large files.
I decided to sit and wait to see if it dies completely on its own (as opposed to me xkill-ing it), and after a whole minute, the file is loaded.
So that solves one problem - the file is being loaded. However, why would Emacs take so long to do it? I have no strange settings enabled that should cause it to lag more than usual.
have you hilit-mode on?
with hilit-auto-highlight-maxout and a great value?
I have had the same problem with header-files, so reduce that value.
maybe it is hs-mode (hideshow-mode)?