nonbreakablespace

nonbreakablespace

[Aditya Mahajan]

Hi,
  Suddenly nonbreakablespace stopped working for me :-( It works in the 
garden so I guess that something is wrong in my setup. Can someone 
test whether this compiles fine at their end?

\starttext
A~B
\stoptext

For me, this makes context hang!!

Aditya

Re: nonbreakablespace

[Sanjoy Mahajan]

> \starttext
> A~B
> \stoptext

It works fine here with vanilla ConTeXt ver 2006.08.08 21:51, texexec
6.2.0, tetex 3.0 on Ubuntu (generating pdf).

> For me, this makes context hang!!

Where does it hang?  Running tex or pdftex, or in texexec?

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

Re: nonbreakablespace

[Aditya Mahajan]

On Wed, 16 Aug 2006, Sanjoy Mahajan wrote:

>> \starttext
>> A~B
>> \stoptext
>
> It works fine here with vanilla ConTeXt ver 2006.08.08 21:51, texexec
> 6.2.0, tetex 3.0 on Ubuntu (generating pdf).
>
>> For me, this makes context hang!!
>
> Where does it hang?  Running tex or pdftex, or in texexec?

Running texexec. Everything else is running fine, so I can not figure 
out why this is happening.

Aditya

Re: nonbreakablespace

[Taco Hoekwater]

Aditya Mahajan wrote:
> On Wed, 16 Aug 2006, Sanjoy Mahajan wrote:
> 
> 
>>>\starttext
>>>A~B
>>>\stoptext
>>
>>It works fine here with vanilla ConTeXt ver 2006.08.08 21:51, texexec
>>6.2.0, tetex 3.0 on Ubuntu (generating pdf).
>>
>>
>>>For me, this makes context hang!!
>>
>>Where does it hang?  Running tex or pdftex, or in texexec?
> 
> 
> Running texexec. Everything else is running fine, so I can not figure 
> out why this is happening.

If you can't interrupt the process, try adding \tracingall to your
input. It will generate lots and lots of output, and you will probably
see an expansion loop occuring (if not, then it may be a ruby issue).

Cheers, taco

Re: nonbreakablespace

[Hans Hagen]

Taco Hoekwater wrote:
> Aditya Mahajan wrote:
>   
>> On Wed, 16 Aug 2006, Sanjoy Mahajan wrote:
>>
>>
>>     
>>>> \starttext
>>>> A~B
>>>> \stoptext
>>>>         
>>> It works fine here with vanilla ConTeXt ver 2006.08.08 21:51, texexec
>>> 6.2.0, tetex 3.0 on Ubuntu (generating pdf).
>>>
>>>
>>>       
>>>> For me, this makes context hang!!
>>>>         
>>> Where does it hang?  Running tex or pdftex, or in texexec?
>>>       
>> Running texexec. Everything else is running fine, so I can not figure 
>> out why this is happening.
>>     
>
> If you can't interrupt the process, try adding \tracingall to your
> input. It will generate lots and lots of output, and you will probably
> see an expansion loop occuring (if not, then it may be a ruby issue).
>
>   
i just ran into the loop as well, 

it has to do with a change in load order of modules, i'll fix it (i'm trying to get rid of funny dependencies and this alpha/beta release was actually for taco's eyes only -) 

Hans 


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

Re: nonbreakablespace

[Aditya Mahajan]

On Wed, 16 Aug 2006, Hans Hagen wrote:

> Taco Hoekwater wrote:
>> Aditya Mahajan wrote:
>>
>>> On Wed, 16 Aug 2006, Sanjoy Mahajan wrote:
>>>
>>>
>>>
>>>>> \starttext
>>>>> A~B
>>>>> \stoptext
>>>>>
>>>> It works fine here with vanilla ConTeXt ver 2006.08.08 21:51, texexec
>>>> 6.2.0, tetex 3.0 on Ubuntu (generating pdf).
>>>>
>>>>
>>>>
>>>>> For me, this makes context hang!!
>>>>>
>>>> Where does it hang?  Running tex or pdftex, or in texexec?
>>>>
>>> Running texexec. Everything else is running fine, so I can not figure
>>> out why this is happening.
>>>
>>
>> If you can't interrupt the process, try adding \tracingall to your
>> input. It will generate lots and lots of output, and you will probably
>> see an expansion loop occuring (if not, then it may be a ruby issue).
>>
>>
> i just ran into the loop as well,
>
> it has to do with a change in load order of modules, i'll fix it

It works fine with the new version.


> (i'm trying to get rid of funny dependencies and this alpha/beta 
> release was actually for taco's eyes only -)

I should start taking your warning more seriously :)

Aditya