Re: LDN
On 07-Mar-2000 Allan Rae wrote: I'm still waiting for Lars or Jürgen to write a paragraph or three about why Insets are cool and what they're doing to them. Don't worry about the quality of the writing I clean it up a bit if needed. Well I really don't know what to tell you here #:O) Inset's are cool because it's something new and I like coding new interesting stuff which is a bit tricky to get on :) Inset's will help to clean up a lot of source and remove a lot of hacks we actually have in the code (Footnotes, tabulars, minipages, ...) and they may be easier to handle with and so give (maybe) a better visual feedback (I'm talking of minipages and tabulars). We have reached a maximum amount of hacks we put in the core to have some features we want and now it's time to clean up and remove some of the hacks coding the stuff the right way. Well and there may be also stuff like the ERT inset which hides the EVIL RED TEXT (say LaTeX) from the fast looking Eye and people can make templates with LaTeX in them without scaring people when the see all that command syntax at the first look they take when they load the template. But I think the most important thing for me is I like coding text-insets #:O) Greets Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug I know things about TROY DONAHUE that can't even be PRINTED!! -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
srcdoc
I've just been reading the Rules on creating code for LyX. In this file is the paragraph: - You make the documentation by doing "make srcdoc" in the root, and then you'll find HTML in the srcdoc/ directory. Read with Netscape for best results. Well, it doesn't work! (In neither the main lyx-devel branch of CVS nor the rae branch.) make: *** No rule to make target `srcdoc'. Stop. In fact, the only mention of `srcdoc' that I could find at all is in OLD-CHANGES. Has this option been removed or am I just messing up. If it should work, then what tools will I need to compile it. Many thanks, Angus
trivial bug in insettext.C
+#include algorithm using std::min; using std::max; Won't compile otherwise. A
RE: trivial bug in insettext.C
On 07-Mar-2000 Angus Leeming wrote: +#include algorithm using std::min; using std::max; Won't compile otherwise. Well where would it not compile otherwise? As a matter of fact it does here without that :) Maybe we need some configure-magic (Jean-Marc, Lars)? Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug So, is the glass half empty, half full, or just twice as large as it needs to be? -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
coding rules
I'd like to use development/Code_rules in some modified version for internal (more or less educational) purposes. I would of course include a small header concerning the origin of the document. Does anybody feel that this is not a good thing do? Andre' -- It'll take a long time to eat 63.000 peanuts. André Pönitz . [EMAIL PROTECTED]
RE: coding rules
On 07-Mar-2000 Andre Poenitz wrote: I'd like to use development/Code_rules in some modified version for internal (more or less educational) purposes. I would of course include a small header concerning the origin of the document. Does anybody feel that this is not a good thing do? I would say feel free to use it :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug All progress is based upon a universal innate desire of every organism to live beyond its income. -- Samuel Butler, "Notebooks" -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Re: TOC Problem isolated
"Kayvan" == Kayvan A Sylvan [EMAIL PROTECTED] writes: Kayvan This will probably be more useful to you. Kayvan The problem only appears when you have a multi-line "Abstract" Kayvan in the article class. I still don't know why, and I need to Kayvan get back to working on the paper for now. Hopefully Lars or Kayvan somebody else can track this down now that it's in a small Kayvan test-case. It seems that the problem is rather related to the line breaks on the top and bottom of the table of contents. What seems to happen is that, when you click on the inset, the window is scrolled to show the whole paragraph (top page break + TOC + bottom page break) but the algorithm which does that is not really invariant... Concerning the second example, it exhibits the same problems, provided you resize vertically the window to be small enough. In fact, the document has to be scrolled such that the bottom page break is just at the bottom of the workarea. Lars, does this ring a bell? LyX 1.1.4fix1 does not exhibit this problem (I mean, the TOC moves at the first click, but you can get it at the second one...). JMarc
Re: Problem with dead keys
"Jacques" == Jacques B Siboni [EMAIL PROTECTED] writes:
Jacques But presently the problem occurs with lyx editor: generation
Jacques of accented characters is ok 'e leads to é `e leads to è "e
Jacques leads to ë but generation of standard apostrophe, double
Jacques quote, caret (^), tilde and back quote are impossible. Lyx
Jacques refuses I get the accent that would be upon a character.
Jacques Generated LateX is \i \'{ } instead of '
Hello,
I can confirm this problem, which existed already in 1.0.3, as far as
I can tell.
Jacques I believe it is a known problem.
No, it was not. Thanks for reporting it. I have moved the discussion
to lyx-devel so that a fix can be devised.
Lars, I do not understand the use of the isDeadEvent() function in
lyxlookup. I thought at the time that it was to avoid a clash with our
own dead key handling. However, now that I think about it, LyX dead
key handling is done mainly on plain characters. For example,
\kmod ' acute aAcCeEiIjJlLnNoOsSuUzZ
will act on a real ascii quote character, not on a ' dead key. So, why
is it necessary to filter dead key events at all?
JMarc
Re: srcdoc
Angus Leeming [EMAIL PROTECTED] writes: | I've just been reading the Rules on creating code for LyX. | In this file is the paragraph: | - You make the documentation by doing "make srcdoc" in the root, | and then you'll find HTML in the srcdoc/ directory. Read with | Netscape for best results. | | Well, it doesn't work! (In neither the main lyx-devel | branch of CVS nor the rae branch.) | make: *** No rule to make target `srcdoc'. Stop. | | In fact, the only mention of `srcdoc' that I could find at | all is in OLD-CHANGES. | | Has this option been removed or am I just messing up. If it | should work, then what tools will I need to compile it. It is more that it has never been rewritten for the new autoconf/automake configuration. The Doc++ tool should be all that is needed. But we need a target in the makefile before it will work as documented. Lgb
Re: trivial bug in insettext.C
Juergen Vigna [EMAIL PROTECTED] writes: | On 07-Mar-2000 Angus Leeming wrote: | +#include algorithm | using std::min; | using std::max; | | Won't compile otherwise. | | Well where would it not compile otherwise? | | As a matter of fact it does here without that :) | | Maybe we need some configure-magic (Jean-Marc, Lars)? No, just include the header. Seems that some C++ header is pulling the algorithm header and on other systems it is not. Lgb
Re: coding rules
Andre Poenitz [EMAIL PROTECTED] writes: | I'd like to use development/Code_rules in some modified version for | internal (more or less educational) purposes. I would of course include a | small header concerning the origin of the document. | | Does anybody feel that this is not a good thing do? Just use it. Lgb
Re: lyx-1.1.5cvs bug: All protected spaces export as ~
"Kayvan A. Sylvan" [EMAIL PROTECTED] writes: | | No it doesen't but it absolutely should. The best (less maintence | problems) would be if this knwledge about the surounding envronment | could be done with arguments. | | | Do you want to make that change or should I? | | I can easily pass the freespacing bool around when the inset-latex() functions | get called. Is the freespacing bool enough? Ot should we rather pass a pointer to the surrounding paragraph parameters? Lgb
Re: LDN future plans
On 6 Mar 2000, Jean-Marc Lasgouttes wrote: Another point. The redirect from news/ to the latest LDN is such that I cannot press back from the LDN to go where I was before. This is annoying... It certainly is isn't it. Anyone a html guru who can tell me what to do to avoid this? I expect there's some sort of meta tag to handle this -- tell the browser to forget this url and only remember the redirection target, perhaps? Allan. (ARRae)
Re: LDN future plans
Allan Rae [EMAIL PROTECTED] writes: | On 6 Mar 2000, Jean-Marc Lasgouttes wrote: | | Another point. The redirect from news/ to the latest LDN is such that | I cannot press back from the LDN to go where I was before. This is | annoying... | | It certainly is isn't it. Anyone a html guru who can tell me what to do | to avoid this? I expect there's some sort of meta tag to handle this -- | tell the browser to forget this url and only remember the redirection | target, perhaps? Why can the index file load the news file instead of redirecting to it? Also this redirect should be done in the server not in the html file. Try putting it in the .htaccess file. .htaccess: Redirect index.html 2301.php3 perhaps... Lgb
Re: LDN future plans
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Allan Rae [EMAIL PROTECTED] writes:
|
| | On 6 Mar 2000, Jean-Marc Lasgouttes wrote:
| |
| | Another point. The redirect from news/ to the latest LDN is such that
| | I cannot press back from the LDN to go where I was before. This is
| | annoying...
| |
| | It certainly is isn't it. Anyone a html guru who can tell me what to do
| | to avoid this? I expect there's some sort of meta tag to handle this --
| | tell the browser to forget this url and only remember the redirection
| | target, perhaps?
| |
| | Allan. (ARRae)
|
| I created a index.php3 file that contains _only_ this:
|
| BEGIN_FILE
| ?php
| include("2301.php3");
| ?
| END_FILE
|
| At it seems to work nicely.
| Any objections on using this?
I just did this, change it as needed.
Perhaps when 2301.php3 is included this way the title should be
different than from when you access 2301.php3 directly?
the index.php3 could also contain a function that automatically finds
the current news file so that there will be no need hardcoding it.
Lgb
Re: LDN future plans
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Allan Rae [EMAIL PROTECTED] writes: | | | On 6 Mar 2000, Jean-Marc Lasgouttes wrote: | | | | Another point. The redirect from news/ to the latest LDN is such that | | I cannot press back from the LDN to go where I was before. This is | | annoying... | | | | It certainly is isn't it. Anyone a html guru who can tell me what to do | | to avoid this? I expect there's some sort of meta tag to handle this -- | | tell the browser to forget this url and only remember the redirection | | target, perhaps? | | Why can the index file load the news file instead of redirecting to | it? | | Also this redirect should be done in the server not in the html file. | | Try putting it in the .htaccess file. | | .htaccess: | | Redirect index.html 2301.php3 I tried this, shows the same annoying behaviour. Lgb
Seen this?
http://members.home.net/krobillard/rbook/ a REBOL dialect for writing documents. The dialect was inspired by the LyX document processor. As with LyX, using RBook is a What You See Is What You Mean (WYSIWYM) way of writing documentation. You should read the Lyx user manual or website to learn more about the benefits of WYSIWYM editing. RBook can generate HTML, LyX, and ASCII output. Lgb
lyx rpms...galore
http://rpmfind.net/linux/RPM/lyx.html I have no clue on how they locate rpm's. Lgb
Re: LDN future plans
On 8 Mar 2000, Lars Gullik Bjønnes wrote:
Allan Rae [EMAIL PROTECTED] writes:
| On 6 Mar 2000, Jean-Marc Lasgouttes wrote:
|
| Another point. The redirect from news/ to the latest LDN is such that
| I cannot press back from the LDN to go where I was before. This is
| annoying...
|
| It certainly is isn't it. Anyone a html guru who can tell me what to do
| to avoid this? I expect there's some sort of meta tag to handle this --
| tell the browser to forget this url and only remember the redirection
| target, perhaps?
|
| Allan. (ARRae)
I created a index.php3 file that contains _only_ this:
BEGIN_FILE
?php
include("2301.php3");
?
END_FILE
At it seems to work nicely.
It certainly is a neat trick, however, we still have the problem JMarc was
referring to.
Any objections on using this?
Sure makes for a tiny index.php3 although we may end having to do
something else to overcome the "can't go back" problem.
Allan. (ARRae)
Re: LDN future plans
Allan Rae [EMAIL PROTECTED] writes:
| I created a index.php3 file that contains _only_ this:
|
| BEGIN_FILE
| ?php
| include("2301.php3");
| ?
| END_FILE
|
| At it seems to work nicely.
|
| It certainly is a neat trick, however, we still have the problem JMarc was
| referring to.
|
| Any objections on using this?
|
| Sure makes for a tiny index.php3 although we may end having to do
| something else to overcome the "can't go back" problem.
yes, you need to flush the cache in your browser :-)
Lgb
Re: LDN future plans
On 8 Mar 2000, Lars Gullik Bjønnes wrote:
| I created a index.php3 file that contains _only_ this:
|
| BEGIN_FILE
| ?php
| include("2301.php3");
| ?
| END_FILE
|
| At it seems to work nicely.
Of course the thing I forgot to mention (although I think it's in the
future plans thread) is that I was going to create an index.php3 that
merged the top dozen news items from news.inc with a short blurb about
LDN.
Then LDN.php3 (or current.php3 or latest.php3 haven't decided which
name to use) would either redirect or load the current issue so people
like me who monitor web pages with their wwwoffle can just have one link
to check.
The following:
meta http-equiv="pragma" contents="no-cache"
blocks caching of the page. There may well be something else available
with html-4.0 to block/ignore redirecting pages.
Allan. (ARRae)
Re: LDN future plans
On Wed, 8 Mar 2000, Allan Rae wrote: The following: meta http-equiv="pragma" contents="no-cache" blocks caching of the page. There may well be something else available with html-4.0 to block/ignore redirecting pages. I just downloaded a copy of the latest html-4.01 specification. It has a paragraph saying that redirects via META tags are _bad_ and server side redirects only should be used -- in other words they aren't part of the standard. Allan. (ARRae)
new ostream code
I will begin slowly to remove the code that is dead when USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that in the next two-three days. After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. Fix bugs reported. Another prelease about a week later. Fix bugs reported. Unless something serious. Release lyx 1.1.5 about a week after the last prerelease. Ok, this is my gameplan for the next 2.5 weeks. Lgb
Re: LDN future plans
Allan Rae [EMAIL PROTECTED] writes: | On Wed, 8 Mar 2000, Allan Rae wrote: | The following: | meta http-equiv="pragma" contents="no-cache" | | blocks caching of the page. There may well be something else available | with html-4.0 to block/ignore redirecting pages. | | I just downloaded a copy of the latest html-4.01 specification. It has a | paragraph saying that redirects via META tags are _bad_ and server side | redirects only should be used -- in other words they aren't part of the | standard. What does that give? One point to me? Lgb
Re: LDN
On 07-Mar-2000 Allan Rae wrote: > > I'm still waiting for Lars or Jürgen to write a paragraph or three about > why Insets are cool and what they're doing to them. Don't worry about the > quality of the writing I clean it up a bit if needed. > Well I really don't know what to tell you here #:O) Inset's are cool because it's something new and I like coding new interesting stuff which is a bit tricky to get on :) Inset's will help to clean up a lot of source and remove a lot of hacks we actually have in the code (Footnotes, tabulars, minipages, ...) and they may be easier to handle with and so give (maybe) a better visual feedback (I'm talking of minipages and tabulars). We have reached a maximum amount of hacks we put in the core to have some features we want and now it's time to clean up and remove some of the hacks coding the stuff the right way. Well and there may be also stuff like the ERT inset which hides the EVIL RED TEXT (say LaTeX) from the fast looking Eye and people can make templates with LaTeX in them without scaring people when the see all that command syntax at the first look they take when they load the template. But I think the most important thing for me is I like coding text-insets #:O) Greets Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug I know things about TROY DONAHUE that can't even be PRINTED!! -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
srcdoc
I've just been reading the Rules on creating code for LyX. In this file is the paragraph: - You make the documentation by doing "make srcdoc" in the root, and then you'll find HTML in the srcdoc/ directory. Read with Netscape for best results. Well, it doesn't work! (In neither the main lyx-devel branch of CVS nor the rae branch.) make: *** No rule to make target `srcdoc'. Stop. In fact, the only mention of `srcdoc' that I could find at all is in OLD-CHANGES. Has this option been removed or am I just messing up. If it should work, then what tools will I need to compile it. Many thanks, Angus
trivial bug in insettext.C
+#include using std::min; using std::max; Won't compile otherwise. A
RE: trivial bug in insettext.C
On 07-Mar-2000 Angus Leeming wrote: > +#include > using std::min; > using std::max; > > Won't compile otherwise. Well where would it not compile otherwise? As a matter of fact it does here without that :) Maybe we need some configure-magic (Jean-Marc, Lars)? Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug So, is the glass half empty, half full, or just twice as large as it needs to be? -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
coding rules
I'd like to use development/Code_rules in some modified version for internal (more or less educational) purposes. I would of course include a small header concerning the origin of the document. Does anybody feel that this is not a good thing do? Andre' -- It'll take a long time to eat 63.000 peanuts. André Pönitz . [EMAIL PROTECTED]
RE: coding rules
On 07-Mar-2000 Andre Poenitz wrote: > > I'd like to use development/Code_rules in some modified version for > internal (more or less educational) purposes. I would of course include a > small header concerning the origin of the document. > > Does anybody feel that this is not a good thing do? > I would say feel free to use it :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel:+39-0471-450260 I-39100 Bozen Fax:+39-0471-450296 ITALY Web:http://www.sad.it/~jug All progress is based upon a universal innate desire of every organism to live beyond its income. -- Samuel Butler, "Notebooks" -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Re: TOC Problem isolated
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: Kayvan> This will probably be more useful to you. Kayvan> The problem only appears when you have a multi-line "Abstract" Kayvan> in the article class. I still don't know why, and I need to Kayvan> get back to working on the paper for now. Hopefully Lars or Kayvan> somebody else can track this down now that it's in a small Kayvan> test-case. It seems that the problem is rather related to the line breaks on the top and bottom of the table of contents. What seems to happen is that, when you click on the inset, the window is scrolled to show the whole paragraph (top page break + TOC + bottom page break) but the algorithm which does that is not really invariant... Concerning the second example, it exhibits the same problems, provided you resize vertically the window to be small enough. In fact, the document has to be scrolled such that the bottom page break is just at the bottom of the workarea. Lars, does this ring a bell? LyX 1.1.4fix1 does not exhibit this problem (I mean, the TOC moves at the first click, but you can get it at the second one...). JMarc
Re: Problem with dead keys
> "Jacques" == Jacques B Siboni <[EMAIL PROTECTED]> writes:
Jacques> But presently the problem occurs with lyx editor: generation
Jacques> of accented characters is ok 'e leads to é `e leads to è "e
Jacques> leads to ë but generation of standard apostrophe, double
Jacques> quote, caret (^), tilde and back quote are impossible. Lyx
Jacques> refuses I get the accent that would be upon a character.
Jacques> Generated LateX is \i \'{ } instead of '
Hello,
I can confirm this problem, which existed already in 1.0.3, as far as
I can tell.
Jacques> I believe it is a known problem.
No, it was not. Thanks for reporting it. I have moved the discussion
to lyx-devel so that a fix can be devised.
Lars, I do not understand the use of the isDeadEvent() function in
lyxlookup. I thought at the time that it was to avoid a clash with our
own dead key handling. However, now that I think about it, LyX dead
key handling is done mainly on plain characters. For example,
\kmod ' acute aAcCeEiIjJlLnNoOsSuUzZ
will act on a real ascii quote character, not on a ' dead key. So, why
is it necessary to filter dead key events at all?
JMarc
Re: srcdoc
Angus Leeming <[EMAIL PROTECTED]> writes: | I've just been reading the Rules on creating code for LyX. | In this file is the paragraph: | - You make the documentation by doing "make srcdoc" in the root, | and then you'll find HTML in the srcdoc/ directory. Read with | Netscape for best results. | | Well, it doesn't work! (In neither the main lyx-devel | branch of CVS nor the rae branch.) | make: *** No rule to make target `srcdoc'. Stop. | | In fact, the only mention of `srcdoc' that I could find at | all is in OLD-CHANGES. | | Has this option been removed or am I just messing up. If it | should work, then what tools will I need to compile it. It is more that it has never been rewritten for the new autoconf/automake configuration. The Doc++ tool should be all that is needed. But we need a target in the makefile before it will work as documented. Lgb
Re: trivial bug in insettext.C
Juergen Vigna <[EMAIL PROTECTED]> writes: | On 07-Mar-2000 Angus Leeming wrote: | > +#include | > using std::min; | > using std::max; | > | > Won't compile otherwise. | | Well where would it not compile otherwise? | | As a matter of fact it does here without that :) | | Maybe we need some configure-magic (Jean-Marc, Lars)? No, just include the header. Seems that some C++ header is pulling the algorithm header and on other systems it is not. Lgb
Re: coding rules
Andre Poenitz <[EMAIL PROTECTED]> writes: | I'd like to use development/Code_rules in some modified version for | internal (more or less educational) purposes. I would of course include a | small header concerning the origin of the document. | | Does anybody feel that this is not a good thing do? Just use it. Lgb
Re: lyx-1.1.5cvs bug: All protected spaces export as ~
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > | > No it doesen't but it absolutely should. The best (less maintence | > problems) would be if this knwledge about the surounding envronment | > could be done with arguments. | > | | Do you want to make that change or should I? | | I can easily pass the freespacing bool around when the inset->latex() functions | get called. Is the freespacing bool enough? Ot should we rather pass a pointer to the surrounding paragraph parameters? Lgb
Re: LDN future plans
On 6 Mar 2000, Jean-Marc Lasgouttes wrote: > Another point. The redirect from news/ to the latest LDN is such that > I cannot press back from the LDN to go where I was before. This is > annoying... It certainly is isn't it. Anyone a html guru who can tell me what to do to avoid this? I expect there's some sort of meta tag to handle this -- tell the browser to forget this url and only remember the redirection target, perhaps? Allan. (ARRae)
Re: LDN future plans
Allan Rae <[EMAIL PROTECTED]> writes: | On 6 Mar 2000, Jean-Marc Lasgouttes wrote: | | > Another point. The redirect from news/ to the latest LDN is such that | > I cannot press back from the LDN to go where I was before. This is | > annoying... | | It certainly is isn't it. Anyone a html guru who can tell me what to do | to avoid this? I expect there's some sort of meta tag to handle this -- | tell the browser to forget this url and only remember the redirection | target, perhaps? Why can the index file load the news file instead of redirecting to it? Also this redirect should be done in the server not in the html file. Try putting it in the .htaccess file. .htaccess: Redirect index.html 2301.php3 perhaps... Lgb
Re: LDN future plans
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Allan Rae <[EMAIL PROTECTED]> writes: | | | On 6 Mar 2000, Jean-Marc Lasgouttes wrote: | | | | > Another point. The redirect from news/ to the latest LDN is such that | | > I cannot press back from the LDN to go where I was before. This is | | > annoying... | | | | It certainly is isn't it. Anyone a html guru who can tell me what to do | | to avoid this? I expect there's some sort of meta tag to handle this -- | | tell the browser to forget this url and only remember the redirection | | target, perhaps? | | | | Allan. (ARRae) | | I created a index.php3 file that contains _only_ this: | | BEGIN_FILE | | END_FILE | | At it seems to work nicely. | Any objections on using this? I just did this, change it as needed. Perhaps when 2301.php3 is included this way the title should be different than from when you access 2301.php3 directly? the index.php3 could also contain a function that automatically finds the current news file so that there will be no need hardcoding it. Lgb
Re: LDN future plans
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Allan Rae <[EMAIL PROTECTED]> writes: | | | On 6 Mar 2000, Jean-Marc Lasgouttes wrote: | | | | > Another point. The redirect from news/ to the latest LDN is such that | | > I cannot press back from the LDN to go where I was before. This is | | > annoying... | | | | It certainly is isn't it. Anyone a html guru who can tell me what to do | | to avoid this? I expect there's some sort of meta tag to handle this -- | | tell the browser to forget this url and only remember the redirection | | target, perhaps? | | Why can the index file load the news file instead of redirecting to | it? | | Also this redirect should be done in the server not in the html file. | | Try putting it in the .htaccess file. | | .htaccess: | | Redirect index.html 2301.php3 I tried this, shows the same annoying behaviour. Lgb
Seen this?
http://members.home.net/krobillard/rbook/ a REBOL dialect for writing documents. The dialect was inspired by the LyX document processor. As with LyX, using RBook is a What You See Is What You Mean (WYSIWYM) way of writing documentation. You should read the Lyx user manual or website to learn more about the benefits of WYSIWYM editing. RBook can generate HTML, LyX, and ASCII output. Lgb
lyx rpms...galore
http://rpmfind.net/linux/RPM/lyx.html I have no clue on how they locate rpm's. Lgb
Re: LDN future plans
On 8 Mar 2000, Lars Gullik Bjønnes wrote:
> Allan Rae <[EMAIL PROTECTED]> writes:
>
> | On 6 Mar 2000, Jean-Marc Lasgouttes wrote:
> |
> | > Another point. The redirect from news/ to the latest LDN is such that
> | > I cannot press back from the LDN to go where I was before. This is
> | > annoying...
> |
> | It certainly is isn't it. Anyone a html guru who can tell me what to do
> | to avoid this? I expect there's some sort of meta tag to handle this --
> | tell the browser to forget this url and only remember the redirection
> | target, perhaps?
> |
> | Allan. (ARRae)
>
> I created a index.php3 file that contains _only_ this:
>
> BEGIN_FILE
> include("2301.php3");
> ?>
> END_FILE
>
> At it seems to work nicely.
It certainly is a neat trick, however, we still have the problem JMarc was
referring to.
> Any objections on using this?
Sure makes for a tiny index.php3 although we may end having to do
something else to overcome the "can't go back" problem.
Allan. (ARRae)
Re: LDN future plans
Allan Rae <[EMAIL PROTECTED]> writes:
| > I created a index.php3 file that contains _only_ this:
| >
| > BEGIN_FILE
| > include("2301.php3");
| > ?>
| > END_FILE
| >
| > At it seems to work nicely.
|
| It certainly is a neat trick, however, we still have the problem JMarc was
| referring to.
|
| > Any objections on using this?
|
| Sure makes for a tiny index.php3 although we may end having to do
| something else to overcome the "can't go back" problem.
yes, you need to flush the cache in your browser :-)
Lgb
Re: LDN future plans
On 8 Mar 2000, Lars Gullik Bjønnes wrote:
> | > I created a index.php3 file that contains _only_ this:
> | >
> | > BEGIN_FILE
> | > | > include("2301.php3");
> | > ?>
> | > END_FILE
> | >
> | > At it seems to work nicely.
Of course the thing I forgot to mention (although I think it's in the
future plans thread) is that I was going to create an index.php3 that
merged the top dozen news items from news.inc with a short blurb about
LDN.
Then LDN.php3 (or current.php3 or latest.php3 haven't decided which
name to use) would either redirect or load the current issue so people
like me who monitor web pages with their wwwoffle can just have one link
to check.
The following:
blocks caching of the page. There may well be something else available
with html-4.0 to block/ignore redirecting pages.
Allan. (ARRae)
Re: LDN future plans
On Wed, 8 Mar 2000, Allan Rae wrote: > The following: > > > blocks caching of the page. There may well be something else available > with html-4.0 to block/ignore redirecting pages. I just downloaded a copy of the latest html-4.01 specification. It has a paragraph saying that redirects via META tags are _bad_ and server side redirects only should be used -- in other words they aren't part of the standard. Allan. (ARRae)
new ostream code
I will begin slowly to remove the code that is dead when USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that in the next two-three days. After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. Fix bugs reported. Another prelease about a week later. Fix bugs reported. Unless something serious. Release lyx 1.1.5 about a week after the last prerelease. Ok, this is my gameplan for the next 2.5 weeks. Lgb
Re: LDN future plans
Allan Rae <[EMAIL PROTECTED]> writes: | On Wed, 8 Mar 2000, Allan Rae wrote: | > The following: | > | > | > blocks caching of the page. There may well be something else available | > with html-4.0 to block/ignore redirecting pages. | | I just downloaded a copy of the latest html-4.01 specification. It has a | paragraph saying that redirects via META tags are _bad_ and server side | redirects only should be used -- in other words they aren't part of the | standard. What does that give? One point to me? Lgb
