bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Long Beach Film Festival - Now Accepting Films & Screenplays


From: Robin Duarte
Subject: Long Beach Film Festival - Now Accepting Films & Screenplays
Date: Sat, 20 Jul 2002 18:36:28 -0800

[p l e a s e  f o r w a r d   t o  i n t e r e s t e d   p a r t i e s]

Filmmakers & Screenwriters:

The Long Beach Film Festival is now accepting screenplays and films (short, 
documentary & feature) in all formats.  The winners' work will be reviewed by a 
committee of established production companies.  This is a great way to get 
exposure and even discovered in Hollywood.

The festival is being held onboard the renowned Queen Mary in Long Beach, 
California (30 miles from Hollywood).  The dates of the festival are September 
13 - 22, 2002.

You can view an 8 x 10 flyer here: 
http://www.longbeachfilmfestival.com/poster.html

A 20% discount has been set up for students and independent filmmakers. The 
discounted submission prices are as follows:

ORIGINAL PRICE             DISCOUNTED PRICE
Short Film      $45               $36
Feature Film    $60               $48
Screenplay      $50               $40

To take advantage of these discounted prices, simply include a printout of this 
email with the submission form and legibly write 'email discount' on the 
payment check.

The submission forms can be found here: 
http://www.longbeachfilmfestival.com/entry.htm

All submissions must be received by August 15th, 2002.

We look forward to receiving your work.

Robin Duarte
http://www.longbeachfilmfestival.com


From "-user news"@jekyl.ab.tac.net Sat Jul 20 22:16:34 2002
Received: from sjc3-1.relay.mail.uu.net ([199.171.54.122])
        by fencepost.gnu.org with smtp (Exim 3.35 #1 (Debian))
        id 17W6Gv-0000qv-00
        for <address@hidden>; Sat, 20 Jul 2002 22:16:33 -0400
Received: from jekyl.ab.tac.net by sjc3sosrv11.alter.net with SMTP 
        (peer crosschecked as: jekyl.ab.tac.net [205.233.108.180])
        id QQmykf22323
        for <address@hidden>; Sun, 21 Jul 2002 02:16:33 GMT
Received: (qmail 4427 invoked by uid 300); 21 Jul 2002 02:16:29 -0000
To: address@hidden
Path: not-for-mail
Newsgroups: gnu.emacs.bug
Subject: Re: TAB is something you don't want to send thru *shell*
References: <address@hidden> <address@hidden> <address@hidden>
From: Dale Hagglund <address@hidden>
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 25
Message-ID: <address@hidden>
Date: Sun, 21 Jul 2002 02:16:29 GMT
NNTP-Posting-Host: 209.115.177.34
X-Trace: jekyl.ab.tac.net 1027217789 209.115.177.34 (Sat, 20 Jul 2002 20:16:29 
MDT)
NNTP-Posting-Date: Sat, 20 Jul 2002 20:16:29 MDT
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs>,
        <mailto:address@hidden>
List-Id: Bug reports for GNU Emacs,
        the Swiss army knife of text editors <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs>,
        <mailto:address@hidden>
List-Archive: <http://mail.gnu.org/pipermail/bug-gnu-emacs/>

address@hidden (Andreas Schwab) writes:

> Miles Bader <address@hidden> writes:
> 
> |> address@hidden (Dan Jacobson) writes:
> |> > What is the big problem with TAB in *shell* now (21.2)?
> |> > No matter how you get a TAB into the command line, ^Q^I or paste, you
> |> > are going to get the 329 etc. possibilities treatment:
> |> 
> |> I think this is because the pty emacs uses to communciate with the
> |> shell process is kept in cooked mode, and so it's interpreting any
> |> terminal control characters it gets in the input.
> 
> TAB is not a terminal control character.  It is interpreted by readline,
> because bash does not know that there is already an editing interface
> running on top of it.

I believe that readline interprets ^V as its literal-next-char
escape.  So try the sequence

        C-q C-v C-q TAB

from inside the shell buffer and see if that helps.

Dale Hagglund.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]