all messages for Emacs-related lists mirrored at yhetil.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: Fri, 23 Dec 2016 11:18:32 -0500	[thread overview]
Message-ID: <E1cKSYC-0001Xp-KM@fencepost.gnu.org> (raw)
In-Reply-To: <o3j9fu$2q6$1@blaine.gmane.org> (message from Achim Gratz on Fri,  23 Dec 2016 14:40:18 +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. ]]]

  > > Could you put some JS code into the page that would give the user
  > > a way to specify a different URL for klipse.js?  Perhaps that could
  > > be stored in a cookie or something else in the browser.

  > You could do that by rewriting the page into the form that is then 
  > ultimately displayed in the browser.  But I don't consider that a good 
  > solution as the user doesn't know what's going to happen before trying 
  > to use the file (and not at all if the respective cookie already exists, 
  > which the user might have forgotten about or has been dropped in from 
  > somewhere).

I don't follow the meaning of that text.  For instance, "rewriting the
page into the form that is then ultimately displayed..."  Could you
explain what sort of rewrite you mean?

The JS code I propose would indeed change the page -- but only in a
single detail, the URL for klipse.js.  That change hardly qualifies
as "rewriting".  So what "rewriting" is it?

-- 
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-23 16:18 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=E1cKSYC-0001Xp-KM@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.