Error: Null characters ignored

[vinay.melgiri@gmail.com]

I am using slickedit for long time now. i edited a file and saved it. And tried to compile. it gives me error " Error: Null characters ignored".

I edited the file in vim editor and compiled. it works fine there.
can anyone help me on this???

[chrisant]

Some more information might help someone respond:

What OS is this on?  And what version of the OS?
What version of SlickEdit is this on?
Where is the file, is it on a network share?  If so, what type of network share (e.g. Samba, Windows, etc).

[Matthew]

It would also be helpful to take a peek at the "known good" vim-edited file (in SlickEdit), and show Hex view, just to make sure something strange isn't going on with the file encoding. Switch back to normal text view, do some edits in SlickEdit, save the file, and then re-examine the hex display.

If you're seeing strange sequences show up, then this could be a case of file encoding confusion. The easiest way to clean that up is to open the file again (in SE) and explicitly select the proper encoding. Once you've selected an explicit encoding, SE will remember what you've chosen and use that every time that specific file is opened.

[vinay.melgiri@gmail.com]

Slickedit runs on Windows 7, 64 bit version.
I tried both versions of Slickedit 17.0.2 and 18.0.1
File is in linux system (ubuntu) on samba(version 3.4.7) share i guess.

This is what happens:
I open a "good" vim edited file in slickedit.
switched to 'line hex' view
declare a variable and save it.
no change in hex view as of this stage.
i close and reopen the file again.
now i see the first line of file is being replaced by random characters.
I have attached the pic.

Regarding file encoding setting, i have kept it as auto unicode.

[Matthew]

Thanks for the update. A couple questions, so we can try to reproduce this problem.

1. If you copy this file locally and open it, does the same problem arise? Or is it just when opened via the remote share?

2. Are you opening the file using a UNC path (\\server\share\file.txt), or has this Samba share been mapped as a Windows drive letter?

3. How are you opening the file? Are you using the File>Open dialog, picking from the recent file menu, entering "edit <path>" on the SE command line, etc.

[vinay.melgiri@gmail.com]

1. this does not happen when done locally.
2. it has been mapped as a windows drive.
3. I open the file using slickedit button 'open a file for editing'.

[chrisant]

Sounds like this topic.

As a temporary workaround, invoking SlickEdit with the -s3 invocation option might help.

[vinay.melgiri@gmail.com]

Excellent!!!
Thank you very much chrisant.
problem solved.

[Mike]

You can set an environment variable which will invoke the aforementioned attribute when a new instance is started:
VSLICK=-s3