unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Achim Gratz <Stromeko@Nexgo.DE>
Cc: emacs-devel@gnu.org
Subject: Re: Condition to link to javascript code?
Date: Sun, 25 Dec 2016 15:43:00 -0500	[thread overview]
Message-ID: <E1cLFdE-0008SA-O7@fencepost.gnu.org> (raw)
In-Reply-To: <o3o5jl$ckp$1@blaine.gmane.org> (message from Achim Gratz on Sun,  25 Dec 2016 11:04:40 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > There is no reason for the initial HTML to refer to klipse.js at all.
  > > Since that is a Javascript program, there is no point fetching it at
  > > all unless Javascript is enabled.

  > The script name and the server address have to be recorded somewhere in 
  > the file unless I misunderstood what you are trying to do.

Yes, but they don't have to be included as a link
that would cause a browser to prefetch anything.

They can be included as strings, which get concatenated when used.

-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.




  reply	other threads:[~2016-12-25 20:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  3:01 Condition to link to javascript code? Bastien
2016-12-15  3:41 ` Clément Pit--Claudel
2016-12-15 12:12   ` Bastien
2016-12-17 15:47 ` Richard Stallman
2016-12-18 17:47   ` Bastien Guerry
2016-12-19  7:20     ` Elias Mårtenson
2016-12-19  8:06       ` Bastien Guerry
2016-12-19  8:46         ` Elias Mårtenson
2016-12-19 16:32           ` Bastien Guerry
2016-12-19 16:52             ` Clément Pit--Claudel
2016-12-20 18:15             ` Richard Stallman
2016-12-20 19:10               ` Davis Herring
2016-12-21 17:14                 ` Richard Stallman
2016-12-21 11:28               ` Rasmus
2016-12-21 17:18                 ` Richard Stallman
2016-12-22 10:24                   ` Rasmus
2016-12-22 19:56                     ` Richard Stallman
2016-12-23 13:40                       ` Achim Gratz
2016-12-23 16:18                         ` Richard Stallman
2016-12-24 11:41                           ` Achim Gratz
2016-12-24 18:55                             ` Richard Stallman
2016-12-25 10:04                               ` Achim Gratz
2016-12-25 20:43                                 ` Richard Stallman [this message]
2016-12-22  3:13               ` Christopher Allan Webber
2016-12-22 19:54                 ` Richard Stallman
2016-12-23 13:33                   ` Achim Gratz
2016-12-23 16:18                     ` Richard Stallman
2016-12-19 13:44         ` Stefan Monnier
2016-12-19 13:07     ` Richard Stallman
2016-12-19 17:01       ` Bastien Guerry
2016-12-20 18:16         ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1cLFdE-0008SA-O7@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=Stromeko@Nexgo.DE \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).