Le module mod_rewrite utilise un moteur de réécriture à base de règles, basé sur un interpréteur d'expressions rationnelles PCRE, pour réécrire les URLs à la volée. Par défaut, mod_rewrite met en correspondance une URL avec le système de fichiers. Cependant, on peut aussi l'utiliser pour rediriger une URL vers une autre URL, ou pour invoquer une requête interne à destination du mandataire.

mod_rewrite fournit une méthode souple et puissante pour manipuler les URLs en utilisant un nombre illimité de règles. Chaque règle peut être associée à un nombre illimité de conditions, afin de vous permettre de réécrire les URLs en fonction de variables du serveur, de variables d'environnement, d'en-têtes HTTP, ou de repères temporels.

mod_rewrite agit sur la totalité de l'URL, y compris la partie chemin. Une règle de réécriture peut être invoquée dans httpd.conf ou dans un fichier .htaccess. Le chemin généré par une règle de réécriture peut inclure une chaîne de paramètres, ou peut renvoyer vers un traitement secondaire interne, une redirection vers une requête externe ou vers le mandataire interne.

spammers wishing to promote products or web sites. MediaWiki offers a number of features designed to combat vandalism in general (see); on this page we deal specifically with wiki spam.

The web is (in 2015) a place where security is increasing essential, and always under threat. It is also a space which needs to be consistent, logical, and user-serving. There follow some thoughts following many recent discussions of "HTTPS Everywhere" and points west.

"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.

The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions (PKGBUILDs) that allow you to compile a package from source with makepkg and then install it via pacman. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the community repository. This document explains how users can access and utilize the AUR.

A good number of new packages that enter the official repositories start in the AUR. In the AUR, users are able to contribute their own package builds (PKGBUILD and related files). The AUR community has the ability to vote for or against packages in the AUR. If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the community repository (directly accessible by pacman or abs).

When building packages for Arch Linux, adhere to the package guidelines below, especially if the intention is to contribute a new package to Arch Linux. You should also see the PKGBUILD and makepkg manpages.

The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances. Exception to this strict rule may only be packages having extra features enabled and/or patches in comparison to the official ones. In such an occasion, the pkgname array should be different.

This article aims to assist users creating their own packages using the Arch Linux "ports-like" build system, also for submission in AUR. It covers creation of a PKGBUILD – a package build description file sourced by makepkg to create a binary package from source. If already in possession of a PKGBUILD, see makepkg. For instructions regarding existing rules and ways to improve package quality see Arch packaging standards.

A PKGBUILD is a shell script containing the build information required by Arch Linux packages.

Packages in Arch Linux are built using the makepkg utility. When makepkg is run, it searches for a PKGBUILD file in the current directory and follows the instructions therein to either compile or otherwise acquire the files to build a package archive (pkgname.pkg.tar.xz). The resulting package contains binary files and installation instructions, readily installable with pacman.

Mandatory variables are pkgname, pkgver, pkgrel, and arch. license is not strictly necessary to build a package, but is recommended for any PKGBUILDs shared with others, as makepkg will produce a warning if not present.

It is a common practice to define the variables in the PKGBUILD in same order as given here. However, this is not mandatory, as long as correct Bash syntax is used.

Yes!

Not only that, we can do one better by using vw and calc.

Simply set the width of the child elements to be 100% of the viewport width by using vw (percentage viewport units), and then set their left margin to a negative calculated value based on this, minus the width of the wrapper. Other than the optional max-width of the parent, everything else is calculated automatically. You can dynamically change the width of the parent container, and the children will automatically resize and align as needed, without being positioned.

<!-- begin snippet: js hide: false -->

<!-- language: lang-css -->

body,
html,
.parent {
  height: 100%;
  width: 100%;
  text-align: center;
  padding: 0;
  margin: 0;
}
.parent {
  width: 50%;
  max-width: 800px;
  background: grey;
  margin: 0 auto;
  position: relative;
}
.child {
  width: 100vw;/* <-- children as wide as the browser window (viewport) */
  margin-left: calc(-1 * ((100vw - 100%) / 2));/* align left edge to the left edge of the viewport */
  /* The above is basically saying to set the left margin to minus the width of the viewport MINUS the width of the parent, divided by two, so the left edge of the viewport */
  height: 50px;
  background: yellow;
}

See also https://stackoverflow.com/questions/5581034/

A more modern solution to this question is to use the viewport unit vw and calc().

Set the width of the child element to 100% of the viewport width, or 100vw. Then move the child element 50% of the viewport width – minus 50% of the parent element's width – to the left to make it meet the edge of the screen.

.child-element {
    position: relative;
    width: 100vw;
    left: calc(-50vw + 50%);
}

With this, the position type of the parent element doesn't matter and the child element is still part of the content flow.

Here's a demo.

Browser support for vw and for calc() can generally be seen as IE9+.

Note: This assumes the box model is set to border-box. Without border-box, you'll also have to subtract paddings and borders, making this solution a mess.

Why Study Emacs Lisp?

Although Emacs Lisp is usually thought of in association only with Emacs, it is a full computer programming language. You can use Emacs Lisp as you would any other programming language.

Perhaps you want to understand programming; perhaps you want to extend Emacs; or perhaps you want to become a programmer. This introduction to Emacs Lisp is designed to get you started: to guide you in learning the fundamentals of programming, and more importantly, to show you how you can teach yourself to go further.

This page contains snippets of code that demonstrate basic EmacsLisp programming operations in the spirit of the O’Reilly cookbook series of books. For every task addressed, a worked-out solution is presented as a short, focused, directly usable piece of code.

All this stuff can be found elsewhere, but it is scattered about in libraries, manuals, etc. It would be helpful to have here in one spot.

These recipes should be pastable into the scratch buffer so that users can hit ‘C-j’ and evaluate them step by step.

There’s going to be some overlap with CategoryCode, obviously. Just link to more elaborate pages when appropriate. Should this page grow too large, we’ll split it up later.

Key chords is the bane of keyboarding.

There are 3 types of keyboard shortcuts to invoke commands in software:

• ① Single key ➢ for example: 【F1】, 【⇞ Page △】.
• ② Key chord ➢ for example: 【Ctrl+c】, 【Ctrl+⇧ Shift+z】, 【Alt+F4】.
• ③ Key sequence of single keys or chords. ➢ for example: on Microsoft Windows, 【F10 e c】 for copy, or 【Alt+Space c】 to close window.

of these, in terms of efficiency and hand health (Repetitive Strain Injury), the single key is the best. Key sequence of single keys is second best. Key chord is the worst.

Key chord is the most hard on hand health, but is also conceptually the most convoluted.

i remember in around 1991, when i first learned about key chord on the Macintosh Classic. I remember thinking, it's strange. You have to hold ⌘ Cmd first, then press the key c, then, release c, then, release ⌘ Cmd. It must be in that specific order.

A more natural way is either key sequence, or real chords. Real chords, meaning, pressing several keys together but you don't have to worry about which to hold or release first. Stenograph machines are like that.

(A Net Ethology / A Troll's Confection)

 When a person's sanity is at balance,
 when human passion is raging,
 no etiquette must get in the way.
     —Xah Lee, 2001.

The internet has changed society deeply. It has indirectly changed nations, catapulted sciences, deeply imbued the daily lives of men, and as well affected writings and have created a culture one of a kind, among which is FAQ (Frequently Asked Questions), Netiquette, and Trolling. Netiquette refers to Net Etiquette. It is the implicit rules in online communities, widely purveyed in the early days of internet (pre-1997) but faded quietly with the mainstreaming of internet. Troll roughly refers to someone who posts a message that solicit outwardly or indirectly a huge usually chaotic following. In these pages, are collected essays on these phenomena.

I as a troll is rather special because i tend to put a final say on things, in contrast with one-liner trolls i myself despise. (In a sense i'm an anti-troll, untroll, or an atrocious atroll.) At first i balked at being branded a troll. Now i revel it. I as a troll is rather recent, beginning and getting worse about in 1998. I have been using online forums since 1990. Perhaps one day i'll write “how i became a troll”. It is bound to be a tragedy. 
—Xah Lee, 2002.

I'll find a day to massacre them all, And raze their faction and their family… 
    —William Shakespeare, in Titus Andronicus