Angus Leeming [EMAIL PROTECTED] writes:
| Andre Poenitz wrote:
On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
That's a good point, but still I think that skipping the full path and
keeping the filename only would be a good option.
This is not sufficient if you have files
Lars Gullik Bjønnes wrote:
Angus Leeming [EMAIL PROTECTED] writes:
| Andre Poenitz wrote:
On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
That's a good point, but still I think that skipping the full path and
keeping the filename only would be a good option.
This is not
Angus Leeming <[EMAIL PROTECTED]> writes:
| Andre Poenitz wrote:
>
>> On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
>>> That's a good point, but still I think that skipping the full path and
>>> keeping the filename only would be a good option.
>>
>> This is not sufficient if
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Andre Poenitz wrote:
>>
>>> On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
That's a good point, but still I think that skipping the full path and
keeping the filename only would be a good
On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
That's a good point, but still I think that skipping the full path and
keeping the filename only would be a good option.
This is not sufficient if you have files of the same name in different
directories...
Andre'
Andre Poenitz wrote:
On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
That's a good point, but still I think that skipping the full path and
keeping the filename only would be a good option.
This is not sufficient if you have files of the same name in different
On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
> That's a good point, but still I think that skipping the full path and
> keeping the filename only would be a good option.
This is not sufficient if you have files of the same name in different
directories...
Andre'
Andre Poenitz wrote:
> On Wed, Jun 15, 2005 at 09:10:48AM +0200, Stefan Kostner wrote:
>> That's a good point, but still I think that skipping the full path and
>> keeping the filename only would be a good option.
>
> This is not sufficient if you have files of the same name in different
>
Hi Andre,
On Jun 13, 2005, at 9:27 PM, Andre Poenitz wrote:
On Mon, Jun 13, 2005 at 07:42:15PM +0200, Stefan Kostner wrote:
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance dvips:
Hi Andre,
On Jun 13, 2005, at 9:27 PM, Andre Poenitz wrote:
On Mon, Jun 13, 2005 at 07:42:15PM +0200, Stefan Kostner wrote:
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance "dvips:
Stefan == Stefan Kostner [EMAIL PROTECTED] writes:
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely
long causing tools like dvips to crash with either segfault or for
instance dvips: ! out of string space.
Looks like a fundamental limitation. We don't
On Mon, Jun 13, 2005 at 07:42:15PM +0200, Stefan Kostner wrote:
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance dvips: ! out of string space.
Looks like a fundamental
> "Stefan" == Stefan Kostner <[EMAIL PROTECTED]> writes:
>> Stefan Kostner wrote:
>>> This means that the filenames of the eps files can be extremely
>>> long causing tools like dvips to crash with either segfault or for
>>> instance "dvips: ! out of string space".
>> Looks like a
On Mon, Jun 13, 2005 at 07:42:15PM +0200, Stefan Kostner wrote:
> >Stefan Kostner wrote:
> >>This means that the filenames of the eps files can be extremely long
> >>causing tools like dvips to crash with either segfault or
> >>for instance "dvips: ! out of string space".
> >
> >Looks like a
Dear all,
using lyx I experienced the following problem:
When I convert a lyx file containing eps graphic files to ps or pdf
using the menu, there is an error message being created:
Cannot convert file
Error while executing
dvips -t a4 -o 'abc.ps' abc.dvi
This happens only when the lyx
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance dvips: ! out of string space.
Looks like a fundamental limitation. We don't add characters to the path,
just replace them. If your
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance dvips: ! out of string space.
Looks like a fundamental limitation. We don't add characters to the
path,
just replace them. If your
Dear all,
using lyx I experienced the following problem:
When I convert a lyx file containing eps graphic files to ps or pdf
using the menu, there is an error message being created:
Cannot convert file
Error while executing
dvips -t a4 -o 'abc.ps' abc.dvi
This happens only when the lyx
Stefan Kostner wrote:
> This means that the filenames of the eps files can be extremely long
> causing tools like dvips to crash with either segfault or
> for instance "dvips: ! out of string space".
Looks like a fundamental limitation. We don't add characters to the path,
just replace them. If
Stefan Kostner wrote:
This means that the filenames of the eps files can be extremely long
causing tools like dvips to crash with either segfault or
for instance "dvips: ! out of string space".
Looks like a fundamental limitation. We don't add characters to the
path,
just replace them. If
20 matches
Mail list logo
