ERT before first \item inside enumerate environment

[S Shieh]

I would like to achieve in LyX the equivalent of

\begin{frame}{WTF?}
\begin{enumerate}
\conti
\item yada
\end{enumerate}
\end{frame}

But if I put the cursor after 1. and use ctrl-L, \seti appears after 
\item.  If I put the cursor after the frametitle and use ctrl-L, 
\seti appears before \begin{enumerate}


Thanks!

Sanford Shieh
Associate Professor
Department of Philosophy
Wesleyan University
350 High Street
Middletown, CT 06459
USA
(860) 685-3646 (office)
(860) 685-3861 (fax)
<sanford.sh...@wesleyan.edu>
Follow me on Academia.edu  

Re: Added Words Not In Dictionary, Redux

[Jean-Marc Lasgouttes]

Le 08/05/16 à 19:17, Stephan Witt a écrit :

I’ve pasted your email into a new document and switched to Aspell as my
current spell checker backend in LyX. As you’ve described it the "communities’"
are marked as misspelled. Obviously the word „communities“ is a know one and
the problem is the handling of the possessive apostrophe for plural words
with terminal ‚s‘ - this is a problem in the Aspell dictionary or the Aspell
code. I don’t know if Aspell is able to handle this correctly. (BTW, hunspell
isn’t better on my system.)

It might be interesting to adapt what emacs does here.

JMarc


ispell-dictionary-alist is a variable defined in `ispell.el'.
Its value is shown below.

Documentation:
An alist of dictionaries and their associated parameters.

Each element of this list is also a list:

(DICTIONARY-NAME CASECHARS NOT-CASECHARS OTHERCHARS MANY-OTHERCHARS-P
ISPELL-ARGS EXTENDED-CHARACTER-MODE CHARACTER-SET)

DICTIONARY-NAME is a possible string value of variable `ispell-dictionary',
nil means the default dictionary.

CASECHARS is a regular expression of valid characters that comprise a word.

NOT-CASECHARS is the opposite regexp of CASECHARS.

OTHERCHARS is a regexp of characters in the NOT-CASECHARS set but which 
can be
used to construct words in some special way.  If OTHERCHARS characters 
follow

and precede characters from CASECHARS, they are parsed as part of a word,
otherwise they become word-breaks.  As an example in English, assume the
regular expression "[']" for OTHERCHARS.  Then "they're" and
"Steven's" are parsed as single words including the "'" character, but
"Stevens'" does not include the quote character as part of the word.
If you want OTHERCHARS to be empty, use the empty string.
Hint: regexp syntax requires the hyphen to be declared first here.

CASECHARS, NOT-CASECHARS, and OTHERCHARS must be unibyte strings
containing bytes of CHARACTER-SET.  In addition, if they contain
non-ASCII bytes, the regular expression must be a single
`character set' construct that doesn't specify a character range
for non-ASCII bytes.

MANY-OTHERCHARS-P is non-nil when multiple OTHERCHARS are allowed in a word.
Otherwise only a single OTHERCHARS character is allowed to be part of any
single word.

ISPELL-ARGS is a list of additional arguments passed to the ispell
subprocess.

EXTENDED-CHARACTER-MODE should be used when dictionaries are used which
have been configured in an Ispell affix file.  (For example, umlauts
can be encoded as \"a, a\", "a, ...)  Defaults are ~tex and ~nroff
in English.  This has the same effect as the command-line `-T' option.
The buffer Major Mode controls Ispell's parsing in tex or nroff mode,
but the dictionary can control the extended character mode.
Both defaults can be overruled in a buffer-local fashion.  See
`ispell-parsing-keyword' for details on this.

CHARACTER-SET used to encode text sent to the ispell subprocess
when the language uses non-ASCII characters.

Note that with "ispell" as the speller, the CASECHARS and
OTHERCHARS slots of the alist should contain the same character
set as casechars and otherchars in the LANGUAGE.aff file (e.g.,
english.aff).  aspell and hunspell don't have this limitation.

Value:
(("fr" "[[:alpha:]]" "[^[:alpha:]]" "[-'.@]" t nil nil iso-8859-1)
 ("en" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("en_AU" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("en_GB" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("en_CA" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("de" "[[:alpha:]]" "[^[:alpha:]]" "[']" t nil nil iso-8859-1)
 ("es" "[[:alpha:]]" "[^[:alpha:]]" "[-]" nil nil nil iso-8859-1)
 ("it" "[[:alpha:]]" "[^[:alpha:]]" "[-.]" nil nil nil iso-8859-1)
 ("nl" "[[:alpha:]]" "[^[:alpha:]]" "[']" t nil nil iso-8859-1)
 ("sv" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("da" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil nil nil iso-8859-1)
 ("pt" "[[:alpha:]]" "[^[:alpha:]]" "[']" t nil nil iso-8859-1)
 ("pt_BR" "[[:alpha:]]" "[^[:alpha:]]" "[']" t nil nil iso-8859-1)
 ("ru" "[[:alpha:]]" "[^[:alpha:]]" "" nil nil nil iso-8859-1)
 ("pl_PL" "[[:alpha:]]" "[^[:alpha:]]" "[']" t nil nil iso-8859-1))

Re: Added Words Not In Dictionary, Redux

[Stephan Witt]

Am 08.05.2016 um 20:51 schrieb Rich Shepard :
> 
> On Sun, 8 May 2016, Stephan Witt wrote:
> 
>> I’ve pasted your email into a new document and switched to Aspell as my
>> current spell checker backend in LyX.
> 
> Stephen,
> 
>  That's interesting. I use ispell here rather than aspell, but I don't
> recall having this problem years ago with LyX. Perhaps it is a spell-checker
> issue. I'll see if there's a way to contact the ispell developers or a way
> to add words to that dictionary.

now I’m curious how you’re using ispell. The time you’ve reported your problem
for the first time you’ve mentioned you’re using Aspell.

Are you able to say when this problem arose first time? Which version of LyX
started to have it?

Stephan

Re: Added Words Not In Dictionary, Redux

[Rich Shepard]

On Sun, 8 May 2016, Stephan Witt wrote:


I’ve pasted your email into a new document and switched to Aspell as my
current spell checker backend in LyX.


Stephen,

  That's interesting. I use ispell here rather than aspell, but I don't
recall having this problem years ago with LyX. Perhaps it is a spell-checker
issue. I'll see if there's a way to contact the ispell developers or a way
to add words to that dictionary.


I don’t know how to fix it and I think it’s not a task for LyX development.


  Not if it's not related to LyX code. I'll find how to edit the dictionary.

Thanks,

Rich

Re: Added Words Not In Dictionary, Redux

[Stephan Witt]

Am 24.04.2016 um 19:23 schrieb Rich Shepard :
> 
>  A while ago I asked why some words that were marked to be added to my
> personal dictionary were not added, and were highlighted for correction each
> time I ran the spelling checker. I've isolated the cases where this occurs.
> 
>  This happens with only collective possession terms; that is, those with
> the possessive apostrophe to the right of the terminal 's.'
> 
>  For example, the LyX spell checker (perhaps a plug-in?) will accept
> "community's" and "communities", but not "communities'" (the latter
> referring to a trait found in all communities.)
> 
>  Perhaps this can lead to a fix for the next release.

Hi Rich,

I’ve pasted your email into a new document and switched to Aspell as my
current spell checker backend in LyX. As you’ve described it the "communities’"
are marked as misspelled. Obviously the word „communities“ is a know one and
the problem is the handling of the possessive apostrophe for plural words
with terminal ‚s‘ - this is a problem in the Aspell dictionary or the Aspell
code. I don’t know if Aspell is able to handle this correctly. (BTW, hunspell
isn’t better on my system.)

I don’t know how to fix it and I think it’s not a task for LyX development.

But I’m pretty sure it’s impossible to fix this for words you’ve added to
your personal word list. Why this? Because the management of word ends and
suffixes is part of the dictionary files and has to be told to the spell checker
engine explicitly. The mechanism of the personal word lists don’t provide any
interface for these subtle details. The only solution I can think of is to
ignore trailing apostrophes in general. Again I don’t know if this would be
correct for english - I’m a native german speaker.

Regards,
Stephan

Re: Beamer: insert frame before first frame

[Jürgen Spitzmüller]

Am Sonntag, den 08.05.2016, 10:38 +0200 schrieb racoon:
> How would I go about to insert a frame before the first frame in a 
> beamer document? Seems incredibly cumbersome to me.

It is cumbersome. You need to insert a separator and a frame title
manually. The plan was to extend the current environment-split lfun to
environment-split-before, but it has not been done yet.

It is probably possible to come up with a command sequence that
automates the task.

Jürgen

> 
> Best,
> Daniel
> 

Beamer: insert frame before first frame

[racoon]

Hi,

How would I go about to insert a frame before the first frame in a 
beamer document? Seems incredibly cumbersome to me.


Best,
Daniel