I've been using eclipse for a while trying to use idea, but the first thing that comes up is that when Eclipse's project is imported into idea, it launches the Tomcat Discovery report illegal character \65279 error.
Previous Solutions
Google has a bit of information, basically two solutions:
- Compiled with the Eclipse compiler, the method set in IntelliJ idea 10.0 is settings (ctrl+alt+s)->project Setting->compiler->java Complier->use complier Select Eclipse, click OK
- Use EditPlus to remove BOM (editplus version 3.01)
Method: Set the file signature to remove UTF-8 first, then open the file, save as UTF-8
Setup method: Tools, Preferences, file--default encoding: Uft-8,utf-8 ID: Always delete signature
The way it is now
Cite blog, click Transfer
But unfortunately the first method above in the current version does not take effect, and the second approach, I drop God, a project so many files, this processing, then what to get when Ah!!!
But fortunately almighty Google, help me find in the use of VIM batch solution, here is attached method:
can take advantage :args
of and :argdo
command
For example, we use VIM to bulk modify all the files under the D:\aa\ folder, the UTF-8 encoded bomb flag removed, under OSX, such as in ~/eclipse/test/src
, then first into the test directory, and then open vim
:args ./src/**
, the other steps are the same as below
:args d:\aa\**
Note that this uses * * to represent the looping folder
:ar
You can see which target files are currently added
:argdo set nobomb |update!
performs a set nobomb on the files in the args list and then forces the Save
This will remove the BOM header for all documents.
Specific information on the use of args and Argdo, see
:help arglist
See the argument list section for more information
Idea importing Eclipse project with \65279 Error resolution