I think, that this should be default-process-coding-system, but this
could affect other processes. As I remember, we can specify concrete
process-coding-system for concrete processes (I don't remember
On Thu, Apr 19, 2012 at 1:52 PM, Eric M. Ludlam <ericludlam@...> wrote:
> I concur with Alex.
> Is there instead a high level config to change the coding system so that
> this isn't necessary?
> On 04/18/2012 03:38 PM, Alex Ott wrote:
>> Just my 5 cents - I suspect, that this could be not only in parsing
>> gcc's output, but the general case - we're getting output of many
>> tools, that possibly can run under windows
>> 2012/4/18 Алайцев Иннокентий<alaitsev@...>:
>>> I'm new to Emacs and decided to use Cedet for coding on Windows. But I
>>> had a
>>> problem with system include path: it was nil while GCC (MinGW) was in
>>> %PATH%. So I decided to fix it up.
>>> After some work I find out that gcc return strings ended with "\r\n"
>>> functions in semantic-gcc are waiting for "\n" ended strings. The only
>>> fix I
>>> see is changing semantic-gcc-query function. Here is the patch
>>> http://dl.dropbox.com/u/17989265/cedet-semantic-gcc.patch. The first
>>> of fix was edited according to Alex Ott recommendation.
>>> The second thing I've done was adding a hook (add-hook
>>> 'semantic-gcc-setup) to make it work. Without it include paths are empty.
>>> I hope it would help.
>>> If I've done anything wrong please tell me the right direction for
>>> P.S. Sorry for my bad English.
With best wishes, Alex Ott
Tiwtter: alexott_en (English), alexott (Russian)