From: William Case <billlinux@rogers.com>
To: Emacs Orgmode <emacs-orgmode@gnu.org>
Subject: FUD on my part re: downloading revisions?
Date: Tue, 01 Jan 2008 13:45:43 -0500 [thread overview]
Message-ID: <1199213143.3102.18.camel@CASE> (raw)
Hi;
I have tried to amend Pete Phillips' download script so that it works
for me but I have some Fears, Uncertainties and Doubts about whether I
got it right or not. Here are my changes and notes:
#!/bin/bash
# script to automate pulling the latest org from Carsten's site
# PJP pete@smtl.co.uk
# $Revision: 1.1 $
# $Log: update-org.sh,v $
# Revision 1.1 2007/04/26 05:53:54 pete
# Initial revision
#####
# emacs 22.1 on Fedora 8
#####
# directory where the org directory is located
DIR=$HOME/Docs/Work/emacs
ORGDIR=$DIR/org
TMP=/tmp
TMPTAR=$TMP/org.tar.gz
# This is where I my copy of the emacs exicutable is kept/installed.
EMACSBIN=/usr/bin/emacs
#####
# The only place I have a lisp file
# (/usr/share/emacs/22.1/lisp/textmodes/org.elc) is here.
# Do I need or want to create a lisp directory in my home directroy?
# If so, why? I don't have or want a CVS version if I have to climb a
# steep CVS learning curve. I am somewhat familiar with svn.
#####
# you should not need to edit anything else below here
# go to the tmp dir
cd $TMP
# make sure we have the emacs [lisp] dir
mkdir -p $DIR
######
# $DIR = $HOME/Docs/Work/emacs the way I have it set up.
# Is this all right?
#######
# get the tar file ... etc. etc.
Any suggestions, warnings or tips would be appreciated.
--
Regards Bill
next reply other threads:[~2008-01-01 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 18:45 William Case [this message]
2008-01-01 18:56 ` FUD on my part re: downloading revisions? Pete Phillips
2008-01-01 22:12 ` William Case
2008-01-01 22:34 ` [Bulk] " William Case
2008-01-01 23:13 ` Pete Phillips
2008-01-02 0:01 ` William Case
2008-01-02 10:10 ` Adam Spiers
2008-01-01 23:26 ` Adam Spiers
2008-01-02 0:16 ` Bastien
2008-01-02 0:36 ` [Bulk] " William Case
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1199213143.3102.18.camel@CASE \
--to=billlinux@rogers.com \
--cc=emacs-orgmode@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/org-mode.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).