Re: No error message if disks are full?

1999-06-10 Thread Thierry Michalowski

N Vande Casteele wrote:

 Yes, this is the case. I have also encountered this 'problem' -- the file
 written away is 0 bytes and an error message is only printed on the console
 which is not good when running under XWindows since one doesn't bother
 looking at the console output and thus has no way of knowing the file was
 actually not saved.


I know it's just a matter of personal taste, but I personally like the little
"xconsole" program...just have it there around in a corner of your screen...
Another trick can be to use a totally transparent ETerm that does a tail -f
/var/log/messages , so you'll have the messages appearing right in your root
window...
Of course, that means you want to look at all the messages your system sends
to "you" ; which is in my sense not a bad habit...

Regards
Thierry Michalowksi



begin:vcard 
n:Michalowski;Thierry
tel;cell:+33 6 82 93 73 30
tel;home:+41 21 601 35 22
tel;work:+41 21 349 4626
x-mozilla-html:TRUE
org:Edipresse Publications S.A.;Informatique de Production
adr:;;33,av de la gare;Lausanne;;CH-1001;Suisse
version:2.1
email;internet:[EMAIL PROTECTED]
note;quoted-printable:brUnix uis/u user-friendly...br=0D=0AIt is just selective about who its friends are.br
x-mozilla-cpt:;1760
fn:Thierry Michalowski
end:vcard



Re: No error message if disks are full?

1999-06-10 Thread N Vande Casteele

  Yes, this is the case. I have also encountered this 'problem' -- the
file
  written away is 0 bytes and an error message is only printed on the
console
  which is not good when running under XWindows since one doesn't bother
  looking at the console output and thus has no way of knowing the file
was
  actually not saved.
 

 I know it's just a matter of personal taste, but I personally like the
little
 "xconsole" program...just have it there around in a corner of your
screen...
 Another trick can be to use a totally transparent ETerm that does a
tail -f
 /var/log/messages , so you'll have the messages appearing right in your
root
 window...
 Of course, that means you want to look at all the messages your system
sends
 to "you" ; which is in my sense not a bad habit...

You have a point here... I just wasn't aware that there was a way to make
the console message appear in XWindows and that you don't have to Alt-F1
everytime to read them. [I tried the xconsole program but no messages
appeared there while I did get messages on the Alt-F1 screen, am I doing
something wrong?]

But that doesn't take away the fact that writing away a 0 byte Lyx file
could be warned about in Lyx itself. I don't want to blow this whole thing
up but Lyx is so great because even a newbie can use it; newbies however,
mostly aren't aware of "tail -f /var/log/messages" commands... (as the
situation described by Ingo Kloecker illustrated)

Greetings,
Natal VC





Re: No error message if disks are full?

1999-06-10 Thread Tony Greenwood - ext 4668

  I know it's just a matter of personal taste, but I personally like the
 little
  "xconsole" program...just have it there around in a corner of your
 screen...

 You have a point here... I just wasn't aware that there was a way to make
 the console message appear in XWindows and that you don't have to Alt-F1
 everytime to read them. [I tried the xconsole program but no messages
 appeared there while I did get messages on the Alt-F1 screen, am I doing
 something wrong?]

I always used xconsole to watch what Lyx was up to (especially LaTeX
runs etc.) but when I upgraded to RedHat 5.2 I had no output in the
window unless I ran xconsole su'd to root, so I've got out of the
habit now.



Re: No error message if disks are full?

1999-06-10 Thread Thierry Michalowski

N Vande Casteele wrote:

 Yes, this is the case. I have also encountered this 'problem' -- the file
 written away is 0 bytes and an error message is only printed on the console
 which is not good when running under XWindows since one doesn't bother
 looking at the console output and thus has no way of knowing the file was
 actually not saved.


I know it's just a matter of personal taste, but I personally like the little
"xconsole" program...just have it there around in a corner of your screen...
Another trick can be to use a totally transparent ETerm that does a tail -f
/var/log/messages , so you'll have the messages appearing right in your root
window...
Of course, that means you want to look at all the messages your system sends
to "you" ; which is in my sense not a bad habit...

Regards
Thierry Michalowksi



begin:vcard 
n:Michalowski;Thierry
tel;cell:+33 6 82 93 73 30
tel;home:+41 21 601 35 22
tel;work:+41 21 349 4626
x-mozilla-html:TRUE
org:Edipresse Publications S.A.;Informatique de Production
adr:;;33,av de la gare;Lausanne;;CH-1001;Suisse
version:2.1
email;internet:[EMAIL PROTECTED]
note;quoted-printable:brUnix uis/u user-friendly...br=0D=0AIt is just selective about who its friends are.br
x-mozilla-cpt:;1760
fn:Thierry Michalowski
end:vcard



Re: No error message if disks are full?

1999-06-10 Thread N Vande Casteele

  Yes, this is the case. I have also encountered this 'problem' -- the
file
  written away is 0 bytes and an error message is only printed on the
console
  which is not good when running under XWindows since one doesn't bother
  looking at the console output and thus has no way of knowing the file
was
  actually not saved.
 

 I know it's just a matter of personal taste, but I personally like the
little
 "xconsole" program...just have it there around in a corner of your
screen...
 Another trick can be to use a totally transparent ETerm that does a
tail -f
 /var/log/messages , so you'll have the messages appearing right in your
root
 window...
 Of course, that means you want to look at all the messages your system
sends
 to "you" ; which is in my sense not a bad habit...

You have a point here... I just wasn't aware that there was a way to make
the console message appear in XWindows and that you don't have to Alt-F1
everytime to read them. [I tried the xconsole program but no messages
appeared there while I did get messages on the Alt-F1 screen, am I doing
something wrong?]

But that doesn't take away the fact that writing away a 0 byte Lyx file
could be warned about in Lyx itself. I don't want to blow this whole thing
up but Lyx is so great because even a newbie can use it; newbies however,
mostly aren't aware of "tail -f /var/log/messages" commands... (as the
situation described by Ingo Kloecker illustrated)

Greetings,
Natal VC





Re: No error message if disks are full?

1999-06-10 Thread Tony Greenwood - ext 4668

  I know it's just a matter of personal taste, but I personally like the
 little
  "xconsole" program...just have it there around in a corner of your
 screen...

 You have a point here... I just wasn't aware that there was a way to make
 the console message appear in XWindows and that you don't have to Alt-F1
 everytime to read them. [I tried the xconsole program but no messages
 appeared there while I did get messages on the Alt-F1 screen, am I doing
 something wrong?]

I always used xconsole to watch what Lyx was up to (especially LaTeX
runs etc.) but when I upgraded to RedHat 5.2 I had no output in the
window unless I ran xconsole su'd to root, so I've got out of the
habit now.



Re: No error message if disks are full?

1999-06-10 Thread Thierry Michalowski

N Vande Casteele wrote:

> Yes, this is the case. I have also encountered this 'problem' -- the file
> written away is 0 bytes and an error message is only printed on the console
> which is not good when running under XWindows since one doesn't bother
> looking at the console output and thus has no way of knowing the file was
> actually not saved.
>

I know it's just a matter of personal taste, but I personally like the little
"xconsole" program...just have it there around in a corner of your screen...
Another trick can be to use a totally transparent ETerm that does a tail -f
/var/log/messages , so you'll have the messages appearing right in your root
window...
Of course, that means you want to look at all the messages your system sends
to "you" ; which is in my sense not a bad habit...

Regards
Thierry Michalowksi



begin:vcard 
n:Michalowski;Thierry
tel;cell:+33 6 82 93 73 30
tel;home:+41 21 601 35 22
tel;work:+41 21 349 4626
x-mozilla-html:TRUE
org:Edipresse Publications S.A.;Informatique de Production
adr:;;33,av de la gare;Lausanne;;CH-1001;Suisse
version:2.1
email;internet:[EMAIL PROTECTED]
note;quoted-printable:Unix is user-friendly...=0D=0AIt is just selective about who its friends are.
x-mozilla-cpt:;1760
fn:Thierry Michalowski
end:vcard



Re: No error message if disks are full?

1999-06-10 Thread N Vande Casteele

> > Yes, this is the case. I have also encountered this 'problem' -- the
file
> > written away is 0 bytes and an error message is only printed on the
console
> > which is not good when running under XWindows since one doesn't bother
> > looking at the console output and thus has no way of knowing the file
was
> > actually not saved.
> >
>
> I know it's just a matter of personal taste, but I personally like the
little
> "xconsole" program...just have it there around in a corner of your
screen...
> Another trick can be to use a totally transparent ETerm that does a
tail -f
> /var/log/messages , so you'll have the messages appearing right in your
root
> window...
> Of course, that means you want to look at all the messages your system
sends
> to "you" ; which is in my sense not a bad habit...

You have a point here... I just wasn't aware that there was a way to make
the console message appear in XWindows and that you don't have to Alt-F1
everytime to read them. [I tried the xconsole program but no messages
appeared there while I did get messages on the Alt-F1 screen, am I doing
something wrong?]

But that doesn't take away the fact that writing away a 0 byte Lyx file
could be warned about in Lyx itself. I don't want to blow this whole thing
up but Lyx is so great because even a newbie can use it; newbies however,
mostly aren't aware of "tail -f /var/log/messages" commands... (as the
situation described by Ingo Kloecker illustrated)

Greetings,
Natal VC





Re: No error message if disks are full?

1999-06-10 Thread Tony Greenwood - ext 4668

> > I know it's just a matter of personal taste, but I personally like the
> little
> > "xconsole" program...just have it there around in a corner of your
> screen...
>
> You have a point here... I just wasn't aware that there was a way to make
> the console message appear in XWindows and that you don't have to Alt-F1
> everytime to read them. [I tried the xconsole program but no messages
> appeared there while I did get messages on the Alt-F1 screen, am I doing
> something wrong?]

I always used xconsole to watch what Lyx was up to (especially LaTeX
runs etc.) but when I upgraded to RedHat 5.2 I had no output in the
window unless I ran xconsole su'd to root, so I've got out of the
habit now.



No error message if disks are full?

1999-06-09 Thread Ingo Kloecker

Hi,

one of my friends encountered the following problem:
After working with LyX on some document he saved it and quit LyX. Then
he noticed that the filesize of the lyx-file was 0 Bytes (excellent
compression :-)). Unfortunately LyX didn't warn him, that his document
couldn't be saved because there was no space left on /home. So he lost
the work of a whole morning. I haven't checked if there really isn't a
warning (I guess the other users of /home would get a little upset if I
used all space which is left on /home only to confirm this behavior),
but I think the developers should know it.


Regards,
Ingo




Re: No error message if disks are full?

1999-06-09 Thread Jean-Marc Lasgouttes

 "Ingo" == Ingo Kloecker [EMAIL PROTECTED] writes:

Ingo Hi, one of my friends encountered the following problem: After
Ingo working with LyX on some document he saved it and quit LyX. Then
Ingo he noticed that the filesize of the lyx-file was 0 Bytes
Ingo (excellent compression :-)). Unfortunately LyX didn't warn him,
Ingo that his document couldn't be saved because there was no space
Ingo left on /home. So he lost the work of a whole morning. I haven't
Ingo checked if there really isn't a warning (I guess the other users
Ingo of /home would get a little upset if I used all space which is
Ingo left on /home only to confirm this behavior), but I think the
Ingo developers should know it.

Hmmm, this is strange, since LyX checks when closing the file whether
the write was successful (if I understand correctly). The relevant
code is

// Write marker that shows file is complete
fprintf(file, "\n\\the_end\n");
if (file.close()) {
if (flag)
lyxerr.print(_("Error! Could not close file properly: ")
 +  filename);
else
WriteFSAlert(_("Error! Could not close file properly: "),
 filename);
return false;
}

I would think that this returns false as long as a write failed at
some point. Am I wrong? Another possiblity uis that the warning showed
up on console and not as a popup.

It appears that BufferList::write() calls Buffer::writeFile with flag
set to false. Is there a reason for that? I'd think that one would
like to have a popup message in this case.

JMarc



Re: No error message if disks are full?

1999-06-09 Thread N Vande Casteele

 Hmmm, this is strange, since LyX checks when closing the file whether
 the write was successful (if I understand correctly). The relevant
 code is

 // Write marker that shows file is complete
 fprintf(file, "\n\\the_end\n");
 if (file.close()) {
 if (flag)
 lyxerr.print(_("Error! Could not close file
properly: ")
  +  filename);
 else
 WriteFSAlert(_("Error! Could not close file
properly: "),
  filename);
 return false;
 }

 I would think that this returns false as long as a write failed at
 some point. Am I wrong? Another possiblity uis that the warning showed
 up on console and not as a popup.

Yes, this is the case. I have also encountered this 'problem' -- the file
written away is 0 bytes and an error message is only printed on the console
which is not good when running under XWindows since one doesn't bother
looking at the console output and thus has no way of knowing the file was
actually not saved.

Greetings,
Natal VC




No error message if disks are full?

1999-06-09 Thread Ingo Kloecker

Hi,

one of my friends encountered the following problem:
After working with LyX on some document he saved it and quit LyX. Then
he noticed that the filesize of the lyx-file was 0 Bytes (excellent
compression :-)). Unfortunately LyX didn't warn him, that his document
couldn't be saved because there was no space left on /home. So he lost
the work of a whole morning. I haven't checked if there really isn't a
warning (I guess the other users of /home would get a little upset if I
used all space which is left on /home only to confirm this behavior),
but I think the developers should know it.


Regards,
Ingo




Re: No error message if disks are full?

1999-06-09 Thread Jean-Marc Lasgouttes

 "Ingo" == Ingo Kloecker [EMAIL PROTECTED] writes:

Ingo Hi, one of my friends encountered the following problem: After
Ingo working with LyX on some document he saved it and quit LyX. Then
Ingo he noticed that the filesize of the lyx-file was 0 Bytes
Ingo (excellent compression :-)). Unfortunately LyX didn't warn him,
Ingo that his document couldn't be saved because there was no space
Ingo left on /home. So he lost the work of a whole morning. I haven't
Ingo checked if there really isn't a warning (I guess the other users
Ingo of /home would get a little upset if I used all space which is
Ingo left on /home only to confirm this behavior), but I think the
Ingo developers should know it.

Hmmm, this is strange, since LyX checks when closing the file whether
the write was successful (if I understand correctly). The relevant
code is

// Write marker that shows file is complete
fprintf(file, "\n\\the_end\n");
if (file.close()) {
if (flag)
lyxerr.print(_("Error! Could not close file properly: ")
 +  filename);
else
WriteFSAlert(_("Error! Could not close file properly: "),
 filename);
return false;
}

I would think that this returns false as long as a write failed at
some point. Am I wrong? Another possiblity uis that the warning showed
up on console and not as a popup.

It appears that BufferList::write() calls Buffer::writeFile with flag
set to false. Is there a reason for that? I'd think that one would
like to have a popup message in this case.

JMarc



Re: No error message if disks are full?

1999-06-09 Thread N Vande Casteele

 Hmmm, this is strange, since LyX checks when closing the file whether
 the write was successful (if I understand correctly). The relevant
 code is

 // Write marker that shows file is complete
 fprintf(file, "\n\\the_end\n");
 if (file.close()) {
 if (flag)
 lyxerr.print(_("Error! Could not close file
properly: ")
  +  filename);
 else
 WriteFSAlert(_("Error! Could not close file
properly: "),
  filename);
 return false;
 }

 I would think that this returns false as long as a write failed at
 some point. Am I wrong? Another possiblity uis that the warning showed
 up on console and not as a popup.

Yes, this is the case. I have also encountered this 'problem' -- the file
written away is 0 bytes and an error message is only printed on the console
which is not good when running under XWindows since one doesn't bother
looking at the console output and thus has no way of knowing the file was
actually not saved.

Greetings,
Natal VC




No error message if disks are full?

1999-06-09 Thread Ingo Kloecker

Hi,

one of my friends encountered the following problem:
After working with LyX on some document he saved it and quit LyX. Then
he noticed that the filesize of the lyx-file was 0 Bytes (excellent
compression :-)). Unfortunately LyX didn't warn him, that his document
couldn't be saved because there was no space left on /home. So he lost
the work of a whole morning. I haven't checked if there really isn't a
warning (I guess the other users of /home would get a little upset if I
used all space which is left on /home only to confirm this behavior),
but I think the developers should know it.


Regards,
Ingo




Re: No error message if disks are full?

1999-06-09 Thread Jean-Marc Lasgouttes

> "Ingo" == Ingo Kloecker <[EMAIL PROTECTED]> writes:

Ingo> Hi, one of my friends encountered the following problem: After
Ingo> working with LyX on some document he saved it and quit LyX. Then
Ingo> he noticed that the filesize of the lyx-file was 0 Bytes
Ingo> (excellent compression :-)). Unfortunately LyX didn't warn him,
Ingo> that his document couldn't be saved because there was no space
Ingo> left on /home. So he lost the work of a whole morning. I haven't
Ingo> checked if there really isn't a warning (I guess the other users
Ingo> of /home would get a little upset if I used all space which is
Ingo> left on /home only to confirm this behavior), but I think the
Ingo> developers should know it.

Hmmm, this is strange, since LyX checks when closing the file whether
the write was successful (if I understand correctly). The relevant
code is

// Write marker that shows file is complete
fprintf(file, "\n\\the_end\n");
if (file.close()) {
if (flag)
lyxerr.print(_("Error! Could not close file properly: ")
 +  filename);
else
WriteFSAlert(_("Error! Could not close file properly: "),
 filename);
return false;
}

I would think that this returns false as long as a write failed at
some point. Am I wrong? Another possiblity uis that the warning showed
up on console and not as a popup.

It appears that BufferList::write() calls Buffer::writeFile with flag
set to false. Is there a reason for that? I'd think that one would
like to have a popup message in this case.

JMarc



Re: No error message if disks are full?

1999-06-09 Thread N Vande Casteele

> Hmmm, this is strange, since LyX checks when closing the file whether
> the write was successful (if I understand correctly). The relevant
> code is
>
> // Write marker that shows file is complete
> fprintf(file, "\n\\the_end\n");
> if (file.close()) {
> if (flag)
> lyxerr.print(_("Error! Could not close file
properly: ")
>  +  filename);
> else
> WriteFSAlert(_("Error! Could not close file
properly: "),
>  filename);
> return false;
> }
>
> I would think that this returns false as long as a write failed at
> some point. Am I wrong? Another possiblity uis that the warning showed
> up on console and not as a popup.

Yes, this is the case. I have also encountered this 'problem' -- the file
written away is 0 bytes and an error message is only printed on the console
which is not good when running under XWindows since one doesn't bother
looking at the console output and thus has no way of knowing the file was
actually not saved.

Greetings,
Natal VC