anne/lyx_mirror
1
0
Fork 0
mirror of https://git.lyx.org/repos/lyx.git synced 2024-11-22 01:59:02 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

finally get rid of BUGS.lyx

Browse Source 
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@2946 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
Jean-Marc Lasgouttes 2001-10-30 17:05:57 +00:00
parent 3b0329fe27
commit 23870e9920
7 changed files with 24 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2001-10-30 John Levon <moz@compsoc.man.ac.uk>
* README:
* lyx.man: change ref to known bugs
2001-10-03 Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes@inria.fr> 2001-10-03 Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes@inria.fr>
* configure.in: set version here and not in version.h. * configure.in: set version here and not in version.h.

9
README
View File

@ -188,13 +188,12 @@ Internet resources of relevance to LyX
How do I submit a bug report? How do I submit a bug report?
If possible, read the "Known Bugs" document found under the If possible, read the Introduction found under the Help menu in LyX.
Help menu. You'll find detailed info on submitting bug reports You'll find detailed info on submitting bug reports there.
there.
If you can't do that, send details to the LyX Developers mailing If you can't do that, send details to the LyX Developers mailing
list. Don't forget to mention which version you are having list, or use the LyX bug tracker at http://lyxbugs.sf.net/.
problems with! Don't forget to mention which version you are having problems with!
How can I participate in the development of LyX? How can I participate in the development of LyX?

4
lib/ChangeLog
View File

@ -1,3 +1,7 @@
2001-10-30 John Levon <moz@compsoc.man.ac.uk>
* Makefile.am: remove BUGS.lyx mention
2001-10-29 John Levon <moz@compsoc.man.ac.uk> 2001-10-29 John Levon <moz@compsoc.man.ac.uk>
* ui/default.ui: remove Known Bugs entry * ui/default.ui: remove Known Bugs entry

2
lib/Makefile.am
View File

@ -73,7 +73,7 @@ uninstall-local:
dist-hook: dist-hook:
cd ${distdir} ; rm -rf `find . -name \*CVS\*` ; \ cd ${distdir} ; rm -rf `find . -name \*CVS\*` ; \
rm -rf doc/BUGS.lyx doc/.cvsignore; \ rm -rf doc/.cvsignore; \
[ -f doc/UserGuide.lyx ] || { cvs -Q export -r HEAD -d doc lyxdoc || \ [ -f doc/UserGuide.lyx ] || { cvs -Q export -r HEAD -d doc lyxdoc || \
echo "WARNING: Unable to get LyX Documentation from CVS!" ; true ; } echo "WARNING: Unable to get LyX Documentation from CVS!" ; true ; }

4
lyx.man
View File

@ -179,8 +179,8 @@ Full documentation in either native \fBLyX\fR or postscript format.
.SH BUGS/LIMITATIONS .SH BUGS/LIMITATIONS
There are probably still some bugs in \fBLyX\fR. Please report them to There are probably still some bugs in \fBLyX\fR. Please report them to
lyx-devel@lists.lyx.org with detailed info, including which version of lyx-devel@lists.lyx.org with detailed info, including which version of
\fBLyX\fR you use. Consult the "Known Bugs" item under the Help menu \fBLyX\fR you use. Consult the bug-reporting instructions in the
first if possible. Introduction (accessible from the Help menu in LyX) first if possible.
\fBLaTeX\fR import is still not perfect and may produce buggy *.lyx \fBLaTeX\fR import is still not perfect and may produce buggy *.lyx
files. Consult the \fBreLyX\fR documentation. files. Consult the \fBreLyX\fR documentation.

4
src/ChangeLog
View File

@ -1,3 +1,7 @@
2001-10-30 John Levon <moz@compsoc.man.ac.uk>
* lyx_main.C: change ref to known bugs
2001-10-24 Juergen Vigna <jug@sad.it> 2001-10-24 Juergen Vigna <jug@sad.it>
* tabular-old.C (ReadOld): below variable changes reflected. * tabular-old.C (ReadOld): below variable changes reflected.

8
src/lyx_main.C
View File

@ -203,10 +203,10 @@ void error_handler(int err_sig)
case SIGSEGV: case SIGSEGV:
lyxerr << "\nlyx: SIGSEGV signal caught" << endl; lyxerr << "\nlyx: SIGSEGV signal caught" << endl;
lyxerr << lyxerr <<
"Sorry, you have found a bug in LyX." "Sorry, you have found a bug in LyX. "
" If possible, please read 'Known bugs'\n" "Please read the bug-reporting instructions "
"under the Help menu and then send us " "in Help->Introduction and send us a bug report, "
"a full bug report. Thanks!" << endl; "if necessary. Thanks !" << endl;
break; break;
case SIGTERM: case SIGTERM:
// no comments // no comments