Steven Woody | 1 Jul 05:48 2005

Re: Problem With Emacs Lisp Mode

Miles Bader <miles <at> gnu.org> writes:

> "narke" <narkewoody <at> gmail.com> writes:
>> it says, C-e runs the command move-end-of-line
>
> It sounds like you're running CVS Emacs.
>

sure! if this is really a bug, can i be noticed when it is fixed?
Markus Kuhn | 1 Jul 10:00 2005
Picon
Picon

Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?

Pascal Bourguignon <pjb <at> informatimago.com> writes:
|> > I changed
|> >   \usepackage[latin1]{inputenc}
|> > to
|> >   \usepackage{ucs}
|> >   \usepackage[utf8x]{inputenc}
|> > in the preamble, loaded each file, set Emacs to save in UTF8, and
|> > re-saved each file.  It worked like magic.

As long as you use only a ISO 8859 subset of Unicode, using the
complete ucs package is overkill. A simple

  \usepackage[utf8]{inputenc}

will suffice instead on any recent LaTeX installation (e.g., tetex-3.0)
to handle UTF-8 input files. (By the way, it is UTF-8, not UTF8).

Markus

--

-- 
Markus Kuhn, Computer Laboratory, University of Cambridge
http://www.cl.cam.ac.uk/~mgk25/ || CB3 0FD, Great Britain
Adam Funk | 1 Jul 10:23 2005
Picon

Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?

Pascal Bourguignon wrote:

> > But before I do this to my thesis, I'd like to know if it's really that
> > simple or if there are any pitfalls?  If it matters, my thesis contains
> > a lot of occurrences of Swedish special characters in \text{...}
> > commands in math mode.
>
> Not at all.  Before you do this on your thesis, you want to learn
> about the command cp(1).

:-)

It's on CVS.
Adam Funk | 1 Jul 10:26 2005
Picon

Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?

Markus Kuhn wrote:

> As long as you use only a ISO 8859 subset of Unicode, using the
> complete ucs package is overkill. A simple
>
>   \usepackage[utf8]{inputenc}
>
> will suffice instead on any recent LaTeX installation (e.g., tetex-3.0)
> to handle UTF-8 input files. (By the way, it is UTF-8, not UTF8).

I'm only using Western European characters and the occasional Eastern
European one, so I'll try it.

I'll try to remember "[utf8]" but "UTF-8".

--

-- 
Thanks,
Adam
Robin Fairbairns | 1 Jul 10:57 2005
Picon
Picon

Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?

 "Adam Funk" <a24061 <at> yahoo.com> writes:
>Pascal Bourguignon wrote:
>> > But before I do this to my thesis, I'd like to know if it's really that
>> > simple or if there are any pitfalls?  If it matters, my thesis contains
>> > a lot of occurrences of Swedish special characters in \text{...}
>> > commands in math mode.
>>
>> Not at all.  Before you do this on your thesis, you want to learn
>> about the command cp(1).
>
>:-)
>
>It's on CVS.

oh, goodie.  can we all contribute?
--

-- 
Robin (http://www.tex.ac.uk/faq) Fairbairns, Cambridge
Brendan Halpin | 1 Jul 18:04 2005
Picon

smtpmail.el and logging

I normally send mail directly from my machine using the MTA, and
the access to the logs is handy from time to time. 

However, some of my correspondents are on sites which won't accept
mail except from a machine with a valid MX record, which I don't
have. Therefore I sometimes use smtpmail.el, but I miss the
logging. Does smtpmail.el log at all? If so, how and where?

Brendan
--

-- 
Brendan Halpin,  Department of Sociology,  University of Limerick,  Ireland
Tel: w +353-61-213147 f +353-61-202569 h +353-61-338562; Room F2-025 x 3147
mailto:brendan.halpin <at> ul.ie  http://www.ul.ie/sociology/brendan.halpin.html
Kevin Rodgers | 1 Jul 19:00 2005
Picon

Re: smtpmail.el and logging

Brendan Halpin wrote:
 > I normally send mail directly from my machine using the MTA, and
 > the access to the logs is handy from time to time.
 >
 > However, some of my correspondents are on sites which won't accept
 > mail except from a machine with a valid MX record, which I don't
 > have. Therefore I sometimes use smtpmail.el, but I miss the
 > logging. Does smtpmail.el log at all? If so, how and where?

I don't understand why those sites would accept a direct SMTP connection
from your machine but not an SMTP connection via sendmail.  In any case,
smtpmail logs each transaction in the *trace of SMTP session to foo*
buffer, where foo is smtpmail-smtp-server.

For example, I've been using this for years:

(defadvice smtpmail-send-it (around display-trace-buffer activate)
   "If an error is signalled, display the process buffer."
   (condition-case signals-data
       ad-do-it
     (error (shrink-window-if-larger-than-buffer
	    (display-buffer (get-buffer (format "*trace of SMTP session to %s*"
						smtpmail-smtp-server))))
	   (signal (car signals-data) (cdr signals-data)))))

You should be able to advise smtpmail-send-it to append the contents of
the trace buffer to a log file:

(defvar smtpmail-log-file nil
   "If non-nil, the name of the SMTP log file.")
(Continue reading)

Adam Funk | 1 Jul 20:20 2005
Picon

Re: Pitfalls of switching to {ucs} and [utf8x]{inputenc} ?

On Friday 01 July 2005 09:57, Robin Fairbairns wrote:

>  "Adam Funk" <a24061 <at> yahoo.com> writes:
>>Pascal Bourguignon wrote:
>>> > But before I do this to my thesis, I'd like to know if it's really
>>> > that
>>> > simple or if there are any pitfalls?  If it matters, my thesis
>>> > contains a lot of occurrences of Swedish special characters in
>>> > \text{...} commands in math mode.
>>>
>>> Not at all.  Before you do this on your thesis, you want to learn
>>> about the command cp(1).
>>
>>:-)
>>
>>It's on CVS.
> 
> oh, goodie.  can we all contribute?

Depends on how many corrections I have to make!
;-)
Miles Bader | 2 Jul 03:09 2005
Picon

Re: Problem With Emacs Lisp Mode

Steven Woody <anti-spam.narkewoody <at> gmail.com.dont-post-to> writes:
> sure! if this is really a bug, can i be noticed when it is fixed?

The bugs I noticed before (which resembled your bug, though I'm not sure
they're actually the same ones) seem to have been fixed in CVS.

-Miles
--

-- 
自らを空にして、心を開く時、道は開かれる
Stefan Monnier | 2 Jul 05:23 2005
Picon

Re: select 'mode' from command line?

> I'm working witha code that has both fortran 77 and fortran 90 parts. All the 
> files, however, are named *.f, and emacs always opens them with the 'fortran 
> mode', which is actually more fortran77. So, I wonder if there's a way to tell 
> emacs to use a specific 'mode' from the command line, overriding the default 
> definition. Something like:

>  $emacs -f90 my_f90_file.f &

> to force emacs to already open the file with the f90 mode.

Another option than the -*- cookie is to try and autodetect which it is.
I.e. write

     (defun fortran-77-or-90-mode ()
       (if (... check the buffer, looking for special language constructs
            and/or keywords that only exist in one of the two dialects...)
           (fortran-mode)
         (f90-mode)))

-- Stefan

Gmane